User interfaces for managing user interface sharing

ABSTRACT

The present disclosure generally relates to managing user interface sharing. A computer system receives a representation of a first user interface template that specifies an arrangement of user interface elements. The computer system receiving a request to use the first user interface template for a respective computer system that includes a plurality of installed applications. The computer system initiates a process for creating a user interface for the respective computer system using the first user interface template. The process includes, in accordance with a determination that a first application is not available on the respective computer system, displaying an alert indicating that the first application needs to be installed on the respective computer system. The process includes, in accordance with a determination that the first application is available on the respective computer system, forgoing displaying the alert.

CROSS-REFERENCE TO RELATED APPLICATIONS

This application claims the benefit of U.S. Provisional PatentApplication Ser. No. 63/023,149, entitled “USER INTERFACES FOR MANAGINGUSER INTERFACE SHARING”, filed May 11, 2020, the content of which ishereby incorporated by reference in its entirety.

FIELD

The present disclosure relates generally to computer user interfaces,and more specifically to techniques for managing user interface sharing.

BACKGROUND

An electronic device can display user interfaces that include one ormore features. The one or more features of a respective user interfacethat can be customized before being enabled for use on the electronicdevice.

BRIEF SUMMARY

Some techniques for managing user interface sharing using electronicdevices, however, are generally cumbersome and inefficient. For example,some existing techniques use a complex and time-consuming userinterface, which may include multiple key presses or keystrokes.Existing techniques require more time than necessary, wasting user timeand device energy. This latter consideration is particularly importantin battery-operated systems or devices.

Accordingly, the present technique provides electronic devices withfaster, more efficient methods and interfaces for managing userinterface sharing. Such methods and interfaces optionally complement orreplace other methods for managing user interface sharing. Such methodsand interfaces reduce the cognitive burden on a user and produce a moreefficient human-machine interface. For battery-operated computingdevices, such methods and interfaces conserve power and increase thetime between battery charges.

In accordance with some embodiments, a method performed at a computersystem that is in communication with a display generation component isdescribed. The method comprises: receiving a representation of a firstuser interface template that specifies an arrangement of user interfaceelements including a first user interface element corresponding to afirst application and one or more other user interface elementscorresponding to software that is different from the first application;subsequent to receiving the representation of the first user interfacetemplate, receiving a request to use the first user interface templatefor a respective computer system that includes a plurality of installedapplications; and in response to receiving the request to use the firstuser interface template for the respective computer system, initiating aprocess for creating a user interface for the respective computer systemusing the first user interface template, wherein the process forcreating the user interface for the respective computer system using thefirst user interface template includes: in accordance with adetermination that the first application is not available on therespective computer system, displaying, via the display generationcomponent, an alert indicating that the first application needs to beinstalled on the respective computer system in order for the first userinterface template to be used to create a user interface for therespective computer system that includes the first user interfaceelement from the first user interface template; and in accordance with adetermination that the first application is available on the respectivecomputer system, forgoing displaying, via the display generationcomponent, the alert indicating that the first application needs to beinstalled on the respective computer system in order for the first userinterface template to be used to create a user interface for therespective computer system that includes the first user interfaceelement from the first user interface template.

In accordance with some embodiments, a non-transitory computer-readablestorage medium storing one or more programs configured to be executed byone or more processors of computer system that is in communication witha display generation component is described. The one or more programsinclude instructions for: receiving a representation of a first userinterface template that specifies an arrangement of user interfaceelements including a first user interface element corresponding to afirst application and one or more other user interface elementscorresponding to software that is different from the first application;subsequent to receiving the representation of the first user interfacetemplate, receiving a request to use the first user interface templatefor a respective computer system that includes a plurality of installedapplications; and in response to receiving the request to use the firstuser interface template for the respective computer system, initiating aprocess for creating a user interface for the respective computer systemusing the first user interface template, wherein the process forcreating the user interface for the respective computer system using thefirst user interface template includes: in accordance with adetermination that the first application is not available on therespective computer system, displaying, via the display generationcomponent, an alert indicating that the first application needs to beinstalled on the respective computer system in order for the first userinterface template to be used to create a user interface for therespective computer system that includes the first user interfaceelement from the first user interface template; and in accordance with adetermination that the first application is available on the respectivecomputer system, forgoing displaying, via the display generationcomponent, the alert indicating that the first application needs to beinstalled on the respective computer system in order for the first userinterface template to be used to create a user interface for therespective computer system that includes the first user interfaceelement from the first user interface template.

In accordance with some embodiments, a transitory computer-readablestorage medium storing one or more programs configured to be executed byone or more processors of computer system that is in communication witha display generation component is described. The one or more programsinclude instructions for: receiving a representation of a first userinterface template that specifies an arrangement of user interfaceelements including a first user interface element corresponding to afirst application and one or more other user interface elementscorresponding to software that is different from the first application;subsequent to receiving the representation of the first user interfacetemplate, receiving a request to use the first user interface templatefor a respective computer system that includes a plurality of installedapplications; and in response to receiving the request to use the firstuser interface template for the respective computer system, initiating aprocess for creating a user interface for the respective computer systemusing the first user interface template, wherein the process forcreating the user interface for the respective computer system using thefirst user interface template includes: in accordance with adetermination that the first application is not available on therespective computer system, displaying, via the display generationcomponent, an alert indicating that the first application needs to beinstalled on the respective computer system in order for the first userinterface template to be used to create a user interface for therespective computer system that includes the first user interfaceelement from the first user interface template; and in accordance with adetermination that the first application is available on the respectivecomputer system, forgoing displaying, via the display generationcomponent, the alert indicating that the first application needs to beinstalled on the respective computer system in order for the first userinterface template to be used to create a user interface for therespective computer system that includes the first user interfaceelement from the first user interface template.

In accordance with some embodiments, a computer system comprising adisplay generation component, one or more processors, and memory storingone or more programs configured to be executed by the one or moreprocessors is described. The one or more programs including instructionsfor: receiving a representation of a first user interface template thatspecifies an arrangement of user interface elements including a firstuser interface element corresponding to a first application and one ormore other user interface elements corresponding to software that isdifferent from the first application; subsequent to receiving therepresentation of the first user interface template, receiving a requestto use the first user interface template for a respective computersystem that includes a plurality of installed applications; and inresponse to receiving the request to use the first user interfacetemplate for the respective computer system, initiating a process forcreating a user interface for the respective computer system using thefirst user interface template, wherein the process for creating the userinterface for the respective computer system using the first userinterface template includes: in accordance with a determination that thefirst application is not available on the respective computer system,displaying, via the display generation component, an alert indicatingthat the first application needs to be installed on the respectivecomputer system in order for the first user interface template to beused to create a user interface for the respective computer system thatincludes the first user interface element from the first user interfacetemplate; and in accordance with a determination that the firstapplication is available on the respective computer system, forgoingdisplaying, via the display generation component, the alert indicatingthat the first application needs to be installed on the respectivecomputer system in order for the first user interface template to beused to create a user interface for the respective computer system thatincludes the first user interface element from the first user interfacetemplate.

In accordance with some embodiments, a computer system is described. Thecomputer system comprises: a display generation component; means forreceiving a representation of a first user interface template thatspecifies an arrangement of user interface elements including a firstuser interface element corresponding to a first application and one ormore other user interface elements corresponding to software that isdifferent from the first application; means for, subsequent to receivingthe representation of the first user interface template, receiving arequest to use the first user interface template for a respectivecomputer system that includes a plurality of installed applications; andmeans for, in response to receiving the request to use the first userinterface template for the respective computer system, initiating aprocess for creating a user interface for the respective computer systemusing the first user interface template, wherein the process forcreating the user interface for the respective computer system using thefirst user interface template includes: in accordance with adetermination that the first application is not available on therespective computer system, displaying, via the display generationcomponent, an alert indicating that the first application needs to beinstalled on the respective computer system in order for the first userinterface template to be used to create a user interface for therespective computer system that includes the first user interfaceelement from the first user interface template; and in accordance with adetermination that the first application is available on the respectivecomputer system, forgoing displaying, via the display generationcomponent, the alert indicating that the first application needs to beinstalled on the respective computer system in order for the first userinterface template to be used to create a user interface for therespective computer system that includes the first user interfaceelement from the first user interface template.

Executable instructions for performing these functions are, optionally,included in a non-transitory computer-readable storage medium or othercomputer program product configured for execution by one or moreprocessors. Executable instructions for performing these functions are,optionally, included in a transitory computer-readable storage medium orother computer program product configured for execution by one or moreprocessors.

Thus, devices are provided with faster, more efficient methods andinterfaces for managing user interface sharing, thereby increasing theeffectiveness, efficiency, and user satisfaction with such devices. Suchmethods and interfaces may complement or replace other methods formanaging user interface sharing.

DESCRIPTION OF THE FIGURES

For a better understanding of the various described embodiments,reference should be made to the Description of Embodiments below, inconjunction with the following drawings in which like reference numeralsrefer to corresponding parts throughout the figures.

FIG. 1A is a block diagram illustrating a portable multifunction devicewith a touch-sensitive display in accordance with some embodiments.

FIG. 1B is a block diagram illustrating exemplary components for eventhandling in accordance with some embodiments.

FIG. 2 illustrates a portable multifunction device having a touch screenin accordance with some embodiments.

FIG. 3 is a block diagram of an exemplary multifunction device with adisplay and a touch-sensitive surface in accordance with someembodiments.

FIG. 4A illustrates an exemplary user interface for a menu ofapplications on a portable multifunction device in accordance with someembodiments.

FIG. 4B illustrates an exemplary user interface for a multifunctiondevice with a touch-sensitive surface that is separate from the displayin accordance with some embodiments.

FIG. 5A illustrates a personal electronic device in accordance with someembodiments.

FIG. 5B is a block diagram illustrating a personal electronic device inaccordance with some embodiments.

FIGS. 6A-6AB illustrate exemplary user interfaces for managing userinterface sharing using a computer system, in accordance with someembodiments.

FIGS. 7A-7F is a flow diagram illustrating methods of managing userinterface sharing, in accordance with some embodiments.

DESCRIPTION OF EMBODIMENTS

The following description sets forth exemplary methods, parameters, andthe like. It should be recognized, however, that such description is notintended as a limitation on the scope of the present disclosure but isinstead provided as a description of exemplary embodiments.

There is a need for electronic devices that provide efficient methodsand interfaces for managing user interface sharing. For example, thereis a need for user interfaces that enable quick and easy setup of a userinterface that has been shared via a user interface template. Foranother example, there is a need for user interfaces that enableconvenient downloading of an application(s) for which installation maybe needed to complete the setup of a user interface that has been sharedvia a user interface template. For another example, there is a need foruser interfaces that enable the completion of the setup of a userinterface that has been shared via a user interface template withoutinstalling one or more applications that enable respective features ofthe user interface template. Such techniques can reduce the cognitiveburden on a user who accesses user interface sharing, thereby enhancingproductivity. Further, such techniques can reduce processor and batterypower otherwise wasted on redundant user inputs.

Below, FIGS. 1A-1B, 2, 3, 4A-4B, and 5A-5B provide a description ofexemplary devices for performing the techniques for managing eventnotifications. FIGS. 6A-6AB illustrate exemplary user interfaces formanaging user interface sharing using a computer system, in accordancewith some embodiments. FIGS. 7A-7F is a flow diagram illustratingmethods of managing user interface sharing, in accordance with someembodiments. The user interfaces in FIGS. 6A-6AB are used to illustratethe processes described below, including the processes in FIGS. 7A-7F.

Although the following description uses terms “first,” “second,” etc. todescribe various elements, these elements should not be limited by theterms. These terms are only used to distinguish one element fromanother. For example, a first touch could be termed a second touch, and,similarly, a second touch could be termed a first touch, withoutdeparting from the scope of the various described embodiments. The firsttouch and the second touch are both touches, but they are not the sametouch.

The terminology used in the description of the various describedembodiments herein is for the purpose of describing particularembodiments only and is not intended to be limiting. As used in thedescription of the various described embodiments and the appendedclaims, the singular forms “a,” “an,” and “the” are intended to includethe plural forms as well, unless the context clearly indicatesotherwise. It will also be understood that the term “and/or” as usedherein refers to and encompasses any and all possible combinations ofone or more of the associated listed items. It will be furtherunderstood that the terms “includes,” “including,” “comprises,” and/or“comprising,” when used in this specification, specify the presence ofstated features, integers, steps, operations, elements, and/orcomponents, but do not preclude the presence or addition of one or moreother features, integers, steps, operations, elements, components,and/or groups thereof.

The term “if” is, optionally, construed to mean “when” or “upon” or “inresponse to determining” or “in response to detecting,” depending on thecontext. Similarly, the phrase “if it is determined” or “if [a statedcondition or event] is detected” is, optionally, construed to mean “upondetermining” or “in response to determining” or “upon detecting [thestated condition or event]” or “in response to detecting [the statedcondition or event],” depending on the context.

Embodiments of electronic devices, user interfaces for such devices, andassociated processes for using such devices are described. In someembodiments, the device is a portable communications device, such as amobile telephone, that also contains other functions, such as PDA and/ormusic player functions. Exemplary embodiments of portable multifunctiondevices include, without limitation, the iPhone®, iPod Touch®, and iPad®devices from Apple Inc. of Cupertino, Calif. Other portable electronicdevices, such as laptops or tablet computers with touch-sensitivesurfaces (e.g., touch screen displays and/or touchpads), are,optionally, used. It should also be understood that, in someembodiments, the device is not a portable communications device, but isa desktop computer with a touch-sensitive surface (e.g., a touch screendisplay and/or a touchpad). In some embodiments, the electronic deviceis a computer system that is in communication (e.g., via wirelesscommunication, via wired communication) with a display generationcomponent. The display generation component is configured to providevisual output, such as display via a CRT display, display via an LEDdisplay, or display via image projection. In some embodiments, thedisplay generation component is integrated with the computer system. Insome embodiments, the display generation component is separate from thecomputer system. As used herein, “displaying” content includes causingto display the content (e.g., video data rendered or decoded by displaycontroller 156) by transmitting, via a wired or wireless connection,data (e.g., image data or video data) to an integrated or externaldisplay generation component to visually produce the content.

In the discussion that follows, an electronic device that includes adisplay and a touch-sensitive surface is described. It should beunderstood, however, that the electronic device optionally includes oneor more other physical user-interface devices, such as a physicalkeyboard, a mouse, and/or a joystick.

The device typically supports a variety of applications, such as one ormore of the following: a drawing application, a presentationapplication, a word processing application, a website creationapplication, a disk authoring application, a spreadsheet application, agaming application, a telephone application, a video conferencingapplication, an e-mail application, an instant messaging application, aworkout support application, a photo management application, a digitalcamera application, a digital video camera application, a web browsingapplication, a digital music player application, and/or a digital videoplayer application.

The various applications that are executed on the device optionally useat least one common physical user-interface device, such as thetouch-sensitive surface. One or more functions of the touch-sensitivesurface as well as corresponding information displayed on the deviceare, optionally, adjusted and/or varied from one application to the nextand/or within a respective application. In this way, a common physicalarchitecture (such as the touch-sensitive surface) of the deviceoptionally supports the variety of applications with user interfacesthat are intuitive and transparent to the user.

Attention is now directed toward embodiments of portable devices withtouch-sensitive displays. FIG. 1A is a block diagram illustratingportable multifunction device 100 with touch-sensitive display system112 in accordance with some embodiments. Touch-sensitive display 112 issometimes called a “touch screen” for convenience and is sometimes knownas or called a “touch-sensitive display system.” Device 100 includesmemory 102 (which optionally includes one or more computer-readablestorage mediums), memory controller 122, one or more processing units(CPUs) 120, peripherals interface 118, RF circuitry 108, audio circuitry110, speaker 111, microphone 113, input/output (I/O) subsystem 106,other input control devices 116, and external port 124. Device 100optionally includes one or more optical sensors 164. Device 100optionally includes one or more contact intensity sensors 165 fordetecting intensity of contacts on device 100 (e.g., a touch-sensitivesurface such as touch-sensitive display system 112 of device 100).Device 100 optionally includes one or more tactile output generators 167for generating tactile outputs on device 100 (e.g., generating tactileoutputs on a touch-sensitive surface such as touch-sensitive displaysystem 112 of device 100 or touchpad 355 of device 300). Thesecomponents optionally communicate over one or more communication busesor signal lines 103.

As used in the specification and claims, the term “intensity” of acontact on a touch-sensitive surface refers to the force or pressure(force per unit area) of a contact (e.g., a finger contact) on thetouch-sensitive surface, or to a substitute (proxy) for the force orpressure of a contact on the touch-sensitive surface. The intensity of acontact has a range of values that includes at least four distinctvalues and more typically includes hundreds of distinct values (e.g., atleast 256). Intensity of a contact is, optionally, determined (ormeasured) using various approaches and various sensors or combinationsof sensors. For example, one or more force sensors underneath oradjacent to the touch-sensitive surface are, optionally, used to measureforce at various points on the touch-sensitive surface. In someimplementations, force measurements from multiple force sensors arecombined (e.g., a weighted average) to determine an estimated force of acontact. Similarly, a pressure-sensitive tip of a stylus is, optionally,used to determine a pressure of the stylus on the touch-sensitivesurface. Alternatively, the size of the contact area detected on thetouch-sensitive surface and/or changes thereto, the capacitance of thetouch-sensitive surface proximate to the contact and/or changes thereto,and/or the resistance of the touch-sensitive surface proximate to thecontact and/or changes thereto are, optionally, used as a substitute forthe force or pressure of the contact on the touch-sensitive surface. Insome implementations, the substitute measurements for contact force orpressure are used directly to determine whether an intensity thresholdhas been exceeded (e.g., the intensity threshold is described in unitscorresponding to the substitute measurements). In some implementations,the substitute measurements for contact force or pressure are convertedto an estimated force or pressure, and the estimated force or pressureis used to determine whether an intensity threshold has been exceeded(e.g., the intensity threshold is a pressure threshold measured in unitsof pressure). Using the intensity of a contact as an attribute of a userinput allows for user access to additional device functionality that mayotherwise not be accessible by the user on a reduced-size device withlimited real estate for displaying affordances (e.g., on atouch-sensitive display) and/or receiving user input (e.g., via atouch-sensitive display, a touch-sensitive surface, or aphysical/mechanical control such as a knob or a button).

As used in the specification and claims, the term “tactile output”refers to physical displacement of a device relative to a previousposition of the device, physical displacement of a component (e.g., atouch-sensitive surface) of a device relative to another component(e.g., housing) of the device, or displacement of the component relativeto a center of mass of the device that will be detected by a user withthe user's sense of touch. For example, in situations where the deviceor the component of the device is in contact with a surface of a userthat is sensitive to touch (e.g., a finger, palm, or other part of auser's hand), the tactile output generated by the physical displacementwill be interpreted by the user as a tactile sensation corresponding toa perceived change in physical characteristics of the device or thecomponent of the device. For example, movement of a touch-sensitivesurface (e.g., a touch-sensitive display or trackpad) is, optionally,interpreted by the user as a “down click” or “up click” of a physicalactuator button. In some cases, a user will feel a tactile sensationsuch as an “down click” or “up click” even when there is no movement ofa physical actuator button associated with the touch-sensitive surfacethat is physically pressed (e.g., displaced) by the user's movements. Asanother example, movement of the touch-sensitive surface is, optionally,interpreted or sensed by the user as “roughness” of the touch-sensitivesurface, even when there is no change in smoothness of thetouch-sensitive surface. While such interpretations of touch by a userwill be subject to the individualized sensory perceptions of the user,there are many sensory perceptions of touch that are common to a largemajority of users. Thus, when a tactile output is described ascorresponding to a particular sensory perception of a user (e.g., an “upclick,” a “down click,” “roughness”), unless otherwise stated, thegenerated tactile output corresponds to physical displacement of thedevice or a component thereof that will generate the described sensoryperception for a typical (or average) user.

It should be appreciated that device 100 is only one example of aportable multifunction device, and that device 100 optionally has moreor fewer components than shown, optionally combines two or morecomponents, or optionally has a different configuration or arrangementof the components. The various components shown in FIG. 1A areimplemented in hardware, software, or a combination of both hardware andsoftware, including one or more signal processing and/orapplication-specific integrated circuits.

Memory 102 optionally includes high-speed random access memory andoptionally also includes non-volatile memory, such as one or moremagnetic disk storage devices, flash memory devices, or othernon-volatile solid-state memory devices. Memory controller 122optionally controls access to memory 102 by other components of device100.

Peripherals interface 118 can be used to couple input and outputperipherals of the device to CPU 120 and memory 102. The one or moreprocessors 120 run or execute various software programs and/or sets ofinstructions stored in memory 102 to perform various functions fordevice 100 and to process data. In some embodiments, peripheralsinterface 118, CPU 120, and memory controller 122 are, optionally,implemented on a single chip, such as chip 104. In some otherembodiments, they are, optionally, implemented on separate chips.

RF (radio frequency) circuitry 108 receives and sends RF signals, alsocalled electromagnetic signals. RF circuitry 108 converts electricalsignals to/from electromagnetic signals and communicates withcommunications networks and other communications devices via theelectromagnetic signals. RF circuitry 108 optionally includes well-knowncircuitry for performing these functions, including but not limited toan antenna system, an RF transceiver, one or more amplifiers, a tuner,one or more oscillators, a digital signal processor, a CODEC chipset, asubscriber identity module (SIM) card, memory, and so forth. RFcircuitry 108 optionally communicates with networks, such as theInternet, also referred to as the World Wide Web (WWW), an intranetand/or a wireless network, such as a cellular telephone network, awireless local area network (LAN) and/or a metropolitan area network(MAN), and other devices by wireless communication. The RF circuitry 108optionally includes well-known circuitry for detecting near fieldcommunication (NFC) fields, such as by a short-range communicationradio. The wireless communication optionally uses any of a plurality ofcommunications standards, protocols, and technologies, including but notlimited to Global System for Mobile Communications (GSM), Enhanced DataGSM Environment (EDGE), high-speed downlink packet access (HSDPA),high-speed uplink packet access (HSUPA), Evolution, Data-Only (EV-DO),HSPA, HSPA+, Dual-Cell HSPA (DC-HSPDA), long term evolution (LTE), nearfield communication (NFC), wideband code division multiple access(W-CDMA), code division multiple access (CDMA), time division multipleaccess (TDMA), Bluetooth, Bluetooth Low Energy (BTLE), Wireless Fidelity(Wi-Fi) (e.g., IEEE 802.11a, IEEE 802.11b, IEEE 802.11g, IEEE 802.11n,and/or IEEE 802.11ac), voice over Internet Protocol (VoIP), Wi-MAX, aprotocol for e-mail (e.g., Internet message access protocol (IMAP)and/or post office protocol (POP)), instant messaging (e.g., extensiblemessaging and presence protocol (XMPP), Session Initiation Protocol forInstant Messaging and Presence Leveraging Extensions (SIMPLE), InstantMessaging and Presence Service (IMPS)), and/or Short Message Service(SMS), or any other suitable communication protocol, includingcommunication protocols not yet developed as of the filing date of thisdocument.

Audio circuitry 110, speaker 111, and microphone 113 provide an audiointerface between a user and device 100. Audio circuitry 110 receivesaudio data from peripherals interface 118, converts the audio data to anelectrical signal, and transmits the electrical signal to speaker 111.Speaker 111 converts the electrical signal to human-audible sound waves.Audio circuitry 110 also receives electrical signals converted bymicrophone 113 from sound waves. Audio circuitry 110 converts theelectrical signal to audio data and transmits the audio data toperipherals interface 118 for processing. Audio data is, optionally,retrieved from and/or transmitted to memory 102 and/or RF circuitry 108by peripherals interface 118. In some embodiments, audio circuitry 110also includes a headset jack (e.g., 212, FIG. 2). The headset jackprovides an interface between audio circuitry 110 and removable audioinput/output peripherals, such as output-only headphones or a headsetwith both output (e.g., a headphone for one or both ears) and input(e.g., a microphone).

I/O subsystem 106 couples input/output peripherals on device 100, suchas touch screen 112 and other input control devices 116, to peripheralsinterface 118. I/O subsystem 106 optionally includes display controller156, optical sensor controller 158, depth camera controller 169,intensity sensor controller 159, haptic feedback controller 161, and oneor more input controllers 160 for other input or control devices. Theone or more input controllers 160 receive/send electrical signalsfrom/to other input control devices 116. The other input control devices116 optionally include physical buttons (e.g., push buttons, rockerbuttons, etc.), dials, slider switches, joysticks, click wheels, and soforth. In some embodiments, input controller(s) 160 are, optionally,coupled to any (or none) of the following: a keyboard, an infrared port,a USB port, and a pointer device such as a mouse. The one or morebuttons (e.g., 208, FIG. 2) optionally include an up/down button forvolume control of speaker 111 and/or microphone 113. The one or morebuttons optionally include a push button (e.g., 206, FIG. 2). In someembodiments, the electronic device is a computer system that is incommunication (e.g., via wireless communication, via wiredcommunication) with one or more input devices. In some embodiments, theone or more input devices include a touch-sensitive surface (e.g., atrackpad, as part of a touch-sensitive display). In some embodiments,the one or more input devices include one or more camera sensors (e.g.,one or more optical sensors 164 and/or one or more depth camera sensors175), such as for tracking a user's gestures (e.g., hand gestures) asinput. In some embodiments, the one or more input devices are integratedwith the computer system. In some embodiments, the one or more inputdevices are separate from the computer system.

A quick press of the push button optionally disengages a lock of touchscreen 112 or optionally begins a process that uses gestures on thetouch screen to unlock the device, as described in U.S. patentapplication Ser. No. 11/322,549, “Unlocking a Device by PerformingGestures on an Unlock Image,” filed Dec. 23, 2005, U.S. Pat. No.7,657,849, which is hereby incorporated by reference in its entirety. Alonger press of the push button (e.g., 206) optionally turns power todevice 100 on or off. The functionality of one or more of the buttonsare, optionally, user-customizable. Touch screen 112 is used toimplement virtual or soft buttons and one or more soft keyboards.

Touch-sensitive display 112 provides an input interface and an outputinterface between the device and a user. Display controller 156 receivesand/or sends electrical signals from/to touch screen 112. Touch screen112 displays visual output to the user. The visual output optionallyincludes graphics, text, icons, video, and any combination thereof(collectively termed “graphics”). In some embodiments, some or all ofthe visual output optionally corresponds to user-interface objects.

Touch screen 112 has a touch-sensitive surface, sensor, or set ofsensors that accepts input from the user based on haptic and/or tactilecontact. Touch screen 112 and display controller 156 (along with anyassociated modules and/or sets of instructions in memory 102) detectcontact (and any movement or breaking of the contact) on touch screen112 and convert the detected contact into interaction withuser-interface objects (e.g., one or more soft keys, icons, web pages,or images) that are displayed on touch screen 112. In an exemplaryembodiment, a point of contact between touch screen 112 and the usercorresponds to a finger of the user.

Touch screen 112 optionally uses LCD (liquid crystal display)technology, LPD (light emitting polymer display) technology, or LED(light emitting diode) technology, although other display technologiesare used in other embodiments. Touch screen 112 and display controller156 optionally detect contact and any movement or breaking thereof usingany of a plurality of touch sensing technologies now known or laterdeveloped, including but not limited to capacitive, resistive, infrared,and surface acoustic wave technologies, as well as other proximitysensor arrays or other elements for determining one or more points ofcontact with touch screen 112. In an exemplary embodiment, projectedmutual capacitance sensing technology is used, such as that found in theiPhone® and iPod Touch® from Apple Inc. of Cupertino, Calif.

A touch-sensitive display in some embodiments of touch screen 112 is,optionally, analogous to the multi-touch sensitive touchpads describedin the following U.S. Pat. No. 6,323,846 (Westerman et al.), U.S. Pat.No. 6,570,557 (Westerman et al.), and/or U.S. Pat. No. 6,677,932(Westerman), and/or U.S. Patent Publication 2002/0015024A1, each ofwhich is hereby incorporated by reference in its entirety. However,touch screen 112 displays visual output from device 100, whereastouch-sensitive touchpads do not provide visual output.

A touch-sensitive display in some embodiments of touch screen 112 isdescribed in the following applications: (1) U.S. patent applicationSer. No. 11/381,313, “Multipoint Touch Surface Controller,” filed May 2,2006; (2) U.S. patent application Ser. No. 10/840,862, “MultipointTouchscreen,” filed May 6, 2004; (3) U.S. patent application Ser. No.10/903,964, “Gestures For Touch Sensitive Input Devices,” filed Jul. 30,2004; (4) U.S. patent application Ser. No. 11/048,264, “Gestures ForTouch Sensitive Input Devices,” filed Jan. 31, 2005; (5) U.S. patentapplication Ser. No. 11/038,590, “Mode-Based Graphical User InterfacesFor Touch Sensitive Input Devices,” filed Jan. 18, 2005; (6) U.S. patentapplication Ser. No. 11/228,758, “Virtual Input Device Placement On ATouch Screen User Interface,” filed Sep. 16, 2005; (7) U.S. patentapplication Ser. No. 11/228,700, “Operation Of A Computer With A TouchScreen Interface,” filed Sep. 16, 2005; (8) U.S. patent application Ser.No. 11/228,737, “Activating Virtual Keys Of A Touch-Screen VirtualKeyboard,” filed Sep. 16, 2005; and (9) U.S. patent application Ser. No.11/367,749, “Multi-Functional Hand-Held Device,” filed Mar. 3, 2006. Allof these applications are incorporated by reference herein in theirentirety.

Touch screen 112 optionally has a video resolution in excess of 100 dpi.In some embodiments, the touch screen has a video resolution ofapproximately 160 dpi. The user optionally makes contact with touchscreen 112 using any suitable object or appendage, such as a stylus, afinger, and so forth. In some embodiments, the user interface isdesigned to work primarily with finger-based contacts and gestures,which can be less precise than stylus-based input due to the larger areaof contact of a finger on the touch screen. In some embodiments, thedevice translates the rough finger-based input into a precisepointer/cursor position or command for performing the actions desired bythe user.

In some embodiments, in addition to the touch screen, device 100optionally includes a touchpad for activating or deactivating particularfunctions. In some embodiments, the touchpad is a touch-sensitive areaof the device that, unlike the touch screen, does not display visualoutput. The touchpad is, optionally, a touch-sensitive surface that isseparate from touch screen 112 or an extension of the touch-sensitivesurface formed by the touch screen.

Device 100 also includes power system 162 for powering the variouscomponents. Power system 162 optionally includes a power managementsystem, one or more power sources (e.g., battery, alternating current(AC)), a recharging system, a power failure detection circuit, a powerconverter or inverter, a power status indicator (e.g., a light-emittingdiode (LED)) and any other components associated with the generation,management and distribution of power in portable devices.

Device 100 optionally also includes one or more optical sensors 164.FIG. 1A shows an optical sensor coupled to optical sensor controller 158in I/O subsystem 106. Optical sensor 164 optionally includescharge-coupled device (CCD) or complementary metal-oxide semiconductor(CMOS) phototransistors. Optical sensor 164 receives light from theenvironment, projected through one or more lenses, and converts thelight to data representing an image. In conjunction with imaging module143 (also called a camera module), optical sensor 164 optionallycaptures still images or video. In some embodiments, an optical sensoris located on the back of device 100, opposite touch screen display 112on the front of the device so that the touch screen display is enabledfor use as a viewfinder for still and/or video image acquisition. Insome embodiments, an optical sensor is located on the front of thedevice so that the user's image is, optionally, obtained for videoconferencing while the user views the other video conferenceparticipants on the touch screen display. In some embodiments, theposition of optical sensor 164 can be changed by the user (e.g., byrotating the lens and the sensor in the device housing) so that a singleoptical sensor 164 is used along with the touch screen display for bothvideo conferencing and still and/or video image acquisition.

Device 100 optionally also includes one or more depth camera sensors175. FIG. 1A shows a depth camera sensor coupled to depth cameracontroller 169 in I/O subsystem 106. Depth camera sensor 175 receivesdata from the environment to create a three dimensional model of anobject (e.g., a face) within a scene from a viewpoint (e.g., a depthcamera sensor). In some embodiments, in conjunction with imaging module143 (also called a camera module), depth camera sensor 175 is optionallyused to determine a depth map of different portions of an image capturedby the imaging module 143. In some embodiments, a depth camera sensor islocated on the front of device 100 so that the user's image with depthinformation is, optionally, obtained for video conferencing while theuser views the other video conference participants on the touch screendisplay and to capture selfies with depth map data. In some embodiments,the depth camera sensor 175 is located on the back of device, or on theback and the front of the device 100. In some embodiments, the positionof depth camera sensor 175 can be changed by the user (e.g., by rotatingthe lens and the sensor in the device housing) so that a depth camerasensor 175 is used along with the touch screen display for both videoconferencing and still and/or video image acquisition.

Device 100 optionally also includes one or more contact intensitysensors 165. FIG. 1A shows a contact intensity sensor coupled tointensity sensor controller 159 in I/O subsystem 106. Contact intensitysensor 165 optionally includes one or more piezoresistive strain gauges,capacitive force sensors, electric force sensors, piezoelectric forcesensors, optical force sensors, capacitive touch-sensitive surfaces, orother intensity sensors (e.g., sensors used to measure the force (orpressure) of a contact on a touch-sensitive surface). Contact intensitysensor 165 receives contact intensity information (e.g., pressureinformation or a proxy for pressure information) from the environment.In some embodiments, at least one contact intensity sensor is collocatedwith, or proximate to, a touch-sensitive surface (e.g., touch-sensitivedisplay system 112). In some embodiments, at least one contact intensitysensor is located on the back of device 100, opposite touch screendisplay 112, which is located on the front of device 100.

Device 100 optionally also includes one or more proximity sensors 166.FIG. 1A shows proximity sensor 166 coupled to peripherals interface 118.Alternately, proximity sensor 166 is, optionally, coupled to inputcontroller 160 in I/O subsystem 106. Proximity sensor 166 optionallyperforms as described in U.S. patent application Ser. No. 11/241,839,“Proximity Detector In Handheld Device”; Ser. No. 11/240,788, “ProximityDetector In Handheld Device”; Ser. No. 11/620,702, “Using Ambient LightSensor To Augment Proximity Sensor Output”; Ser. No. 11/586,862,“Automated Response To And Sensing Of User Activity In PortableDevices”; and Ser. No. 11/638,251, “Methods And Systems For AutomaticConfiguration Of Peripherals,” which are hereby incorporated byreference in their entirety. In some embodiments, the proximity sensorturns off and disables touch screen 112 when the multifunction device isplaced near the user's ear (e.g., when the user is making a phone call).

Device 100 optionally also includes one or more tactile outputgenerators 167. FIG. 1A shows a tactile output generator coupled tohaptic feedback controller 161 in I/O subsystem 106. Tactile outputgenerator 167 optionally includes one or more electroacoustic devicessuch as speakers or other audio components and/or electromechanicaldevices that convert energy into linear motion such as a motor,solenoid, electroactive polymer, piezoelectric actuator, electrostaticactuator, or other tactile output generating component (e.g., acomponent that converts electrical signals into tactile outputs on thedevice). Contact intensity sensor 165 receives tactile feedbackgeneration instructions from haptic feedback module 133 and generatestactile outputs on device 100 that are capable of being sensed by a userof device 100. In some embodiments, at least one tactile outputgenerator is collocated with, or proximate to, a touch-sensitive surface(e.g., touch-sensitive display system 112) and, optionally, generates atactile output by moving the touch-sensitive surface vertically (e.g.,in/out of a surface of device 100) or laterally (e.g., back and forth inthe same plane as a surface of device 100). In some embodiments, atleast one tactile output generator sensor is located on the back ofdevice 100, opposite touch screen display 112, which is located on thefront of device 100.

Device 100 optionally also includes one or more accelerometers 168. FIG.1A shows accelerometer 168 coupled to peripherals interface 118.Alternately, accelerometer 168 is, optionally, coupled to an inputcontroller 160 in I/O subsystem 106. Accelerometer 168 optionallyperforms as described in U.S. Patent Publication No. 20050190059,“Acceleration-based Theft Detection System for Portable ElectronicDevices,” and U.S. Patent Publication No. 20060017692, “Methods AndApparatuses For Operating A Portable Device Based On An Accelerometer,”both of which are incorporated by reference herein in their entirety. Insome embodiments, information is displayed on the touch screen displayin a portrait view or a landscape view based on an analysis of datareceived from the one or more accelerometers. Device 100 optionallyincludes, in addition to accelerometer(s) 168, a magnetometer and a GPS(or GLONASS or other global navigation system) receiver for obtaininginformation concerning the location and orientation (e.g., portrait orlandscape) of device 100.

In some embodiments, the software components stored in memory 102include operating system 126, communication module (or set ofinstructions) 128, contact/motion module (or set of instructions) 130,graphics module (or set of instructions) 132, text input module (or setof instructions) 134, Global Positioning System (GPS) module (or set ofinstructions) 135, and applications (or sets of instructions) 136.Furthermore, in some embodiments, memory 102 (FIG. 1A) or 370 (FIG. 3)stores device/global internal state 157, as shown in FIGS. 1A and 3.Device/global internal state 157 includes one or more of: activeapplication state, indicating which applications, if any, are currentlyactive; display state, indicating what applications, views or otherinformation occupy various regions of touch screen display 112; sensorstate, including information obtained from the device's various sensorsand input control devices 116; and location information concerning thedevice's location and/or attitude.

Operating system 126 (e.g., Darwin, RTXC, LINUX, UNIX, OS X, iOS,WINDOWS, or an embedded operating system such as VxWorks) includesvarious software components and/or drivers for controlling and managinggeneral system tasks (e.g., memory management, storage device control,power management, etc.) and facilitates communication between varioushardware and software components.

Communication module 128 facilitates communication with other devicesover one or more external ports 124 and also includes various softwarecomponents for handling data received by RF circuitry 108 and/orexternal port 124. External port 124 (e.g., Universal Serial Bus (USB),FIREWIRE, etc.) is adapted for coupling directly to other devices orindirectly over a network (e.g., the Internet, wireless LAN, etc.). Insome embodiments, the external port is a multi-pin (e.g., 30-pin)connector that is the same as, or similar to and/or compatible with, the30-pin connector used on iPod® (trademark of Apple Inc.) devices.

Contact/motion module 130 optionally detects contact with touch screen112 (in conjunction with display controller 156) and othertouch-sensitive devices (e.g., a touchpad or physical click wheel).Contact/motion module 130 includes various software components forperforming various operations related to detection of contact, such asdetermining if contact has occurred (e.g., detecting a finger-downevent), determining an intensity of the contact (e.g., the force orpressure of the contact or a substitute for the force or pressure of thecontact), determining if there is movement of the contact and trackingthe movement across the touch-sensitive surface (e.g., detecting one ormore finger-dragging events), and determining if the contact has ceased(e.g., detecting a finger-up event or a break in contact).Contact/motion module 130 receives contact data from the touch-sensitivesurface. Determining movement of the point of contact, which isrepresented by a series of contact data, optionally includes determiningspeed (magnitude), velocity (magnitude and direction), and/or anacceleration (a change in magnitude and/or direction) of the point ofcontact. These operations are, optionally, applied to single contacts(e.g., one finger contacts) or to multiple simultaneous contacts (e.g.,“multitouch”/multiple finger contacts). In some embodiments,contact/motion module 130 and display controller 156 detect contact on atouchpad.

In some embodiments, contact/motion module 130 uses a set of one or moreintensity thresholds to determine whether an operation has beenperformed by a user (e.g., to determine whether a user has “clicked” onan icon). In some embodiments, at least a subset of the intensitythresholds are determined in accordance with software parameters (e.g.,the intensity thresholds are not determined by the activation thresholdsof particular physical actuators and can be adjusted without changingthe physical hardware of device 100). For example, a mouse “click”threshold of a trackpad or touch screen display can be set to any of alarge range of predefined threshold values without changing the trackpador touch screen display hardware. Additionally, in some implementations,a user of the device is provided with software settings for adjustingone or more of the set of intensity thresholds (e.g., by adjustingindividual intensity thresholds and/or by adjusting a plurality ofintensity thresholds at once with a system-level click “intensity”parameter).

Contact/motion module 130 optionally detects a gesture input by a user.Different gestures on the touch-sensitive surface have different contactpatterns (e.g., different motions, timings, and/or intensities ofdetected contacts). Thus, a gesture is, optionally, detected bydetecting a particular contact pattern. For example, detecting a fingertap gesture includes detecting a finger-down event followed by detectinga finger-up (liftoff) event at the same position (or substantially thesame position) as the finger-down event (e.g., at the position of anicon). As another example, detecting a finger swipe gesture on thetouch-sensitive surface includes detecting a finger-down event followedby detecting one or more finger-dragging events, and subsequentlyfollowed by detecting a finger-up (liftoff) event.

Graphics module 132 includes various known software components forrendering and displaying graphics on touch screen 112 or other display,including components for changing the visual impact (e.g., brightness,transparency, saturation, contrast, or other visual property) ofgraphics that are displayed. As used herein, the term “graphics”includes any object that can be displayed to a user, including, withoutlimitation, text, web pages, icons (such as user-interface objectsincluding soft keys), digital images, videos, animations, and the like.

In some embodiments, graphics module 132 stores data representinggraphics to be used. Each graphic is, optionally, assigned acorresponding code. Graphics module 132 receives, from applicationsetc., one or more codes specifying graphics to be displayed along with,if necessary, coordinate data and other graphic property data, and thengenerates screen image data to output to display controller 156.

Haptic feedback module 133 includes various software components forgenerating instructions used by tactile output generator(s) 167 toproduce tactile outputs at one or more locations on device 100 inresponse to user interactions with device 100.

Text input module 134, which is, optionally, a component of graphicsmodule 132, provides soft keyboards for entering text in variousapplications (e.g., contacts 137, e-mail 140, IM 141, browser 147, andany other application that needs text input).

GPS module 135 determines the location of the device and provides thisinformation for use in various applications (e.g., to telephone 138 foruse in location-based dialing; to camera 143 as picture/video metadata;and to applications that provide location-based services such as weatherwidgets, local yellow page widgets, and map/navigation widgets).

Applications 136 optionally include the following modules (or sets ofinstructions), or a subset or superset thereof:

-   -   Contacts module 137 (sometimes called an address book or contact        list);    -   Telephone module 138;    -   Video conference module 139;    -   E-mail client module 140;    -   Instant messaging (IM) module 141;    -   Workout support module 142;    -   Camera module 143 for still and/or video images;    -   Image management module 144;    -   Video player module;    -   Music player module;    -   Browser module 147;    -   Calendar module 148;    -   Widget modules 149, which optionally include one or more of:        weather widget 149-1, stocks widget 149-2, calculator widget        149-3, alarm clock widget 149-4, dictionary widget 149-5, and        other widgets obtained by the user, as well as user-created        widgets 149-6;    -   Widget creator module 150 for making user-created widgets 149-6;    -   Search module 151;    -   Video and music player module 152, which merges video player        module and music player module;    -   Notes module 153;    -   Map module 154; and/or    -   Online video module 155.

Examples of other applications 136 that are, optionally, stored inmemory 102 include other word processing applications, other imageediting applications, drawing applications, presentation applications,JAVA-enabled applications, encryption, digital rights management, voicerecognition, and voice replication.

In conjunction with touch screen 112, display controller 156,contact/motion module 130, graphics module 132, and text input module134, contacts module 137 are, optionally, used to manage an address bookor contact list (e.g., stored in application internal state 192 ofcontacts module 137 in memory 102 or memory 370), including: addingname(s) to the address book; deleting name(s) from the address book;associating telephone number(s), e-mail address(es), physicaladdress(es) or other information with a name; associating an image witha name; categorizing and sorting names; providing telephone numbers ore-mail addresses to initiate and/or facilitate communications bytelephone 138, video conference module 139, e-mail 140, or IM 141; andso forth.

In conjunction with RF circuitry 108, audio circuitry 110, speaker 111,microphone 113, touch screen 112, display controller 156, contact/motionmodule 130, graphics module 132, and text input module 134, telephonemodule 138 are optionally, used to enter a sequence of characterscorresponding to a telephone number, access one or more telephonenumbers in contacts module 137, modify a telephone number that has beenentered, dial a respective telephone number, conduct a conversation, anddisconnect or hang up when the conversation is completed. As notedabove, the wireless communication optionally uses any of a plurality ofcommunications standards, protocols, and technologies.

In conjunction with RF circuitry 108, audio circuitry 110, speaker 111,microphone 113, touch screen 112, display controller 156, optical sensor164, optical sensor controller 158, contact/motion module 130, graphicsmodule 132, text input module 134, contacts module 137, and telephonemodule 138, video conference module 139 includes executable instructionsto initiate, conduct, and terminate a video conference between a userand one or more other participants in accordance with user instructions.

In conjunction with RF circuitry 108, touch screen 112, displaycontroller 156, contact/motion module 130, graphics module 132, and textinput module 134, e-mail client module 140 includes executableinstructions to create, send, receive, and manage e-mail in response touser instructions. In conjunction with image management module 144,e-mail client module 140 makes it very easy to create and send e-mailswith still or video images taken with camera module 143.

In conjunction with RF circuitry 108, touch screen 112, displaycontroller 156, contact/motion module 130, graphics module 132, and textinput module 134, the instant messaging module 141 includes executableinstructions to enter a sequence of characters corresponding to aninstant message, to modify previously entered characters, to transmit arespective instant message (for example, using a Short Message Service(SMS) or Multimedia Message Service (MMS) protocol for telephony-basedinstant messages or using XMPP, SIMPLE, or IMPS for Internet-basedinstant messages), to receive instant messages, and to view receivedinstant messages. In some embodiments, transmitted and/or receivedinstant messages optionally include graphics, photos, audio files, videofiles and/or other attachments as are supported in an MMS and/or anEnhanced Messaging Service (EMS). As used herein, “instant messaging”refers to both telephony-based messages (e.g., messages sent using SMSor MMS) and Internet-based messages (e.g., messages sent using XMPP,SIMPLE, or IMPS).

In conjunction with RF circuitry 108, touch screen 112, displaycontroller 156, contact/motion module 130, graphics module 132, textinput module 134, GPS module 135, map module 154, and music playermodule, workout support module 142 includes executable instructions tocreate workouts (e.g., with time, distance, and/or calorie burninggoals); communicate with workout sensors (sports devices); receiveworkout sensor data; calibrate sensors used to monitor a workout; selectand play music for a workout; and display, store, and transmit workoutdata.

In conjunction with touch screen 112, display controller 156, opticalsensor(s) 164, optical sensor controller 158, contact/motion module 130,graphics module 132, and image management module 144, camera module 143includes executable instructions to capture still images or video(including a video stream) and store them into memory 102, modifycharacteristics of a still image or video, or delete a still image orvideo from memory 102.

In conjunction with touch screen 112, display controller 156,contact/motion module 130, graphics module 132, text input module 134,and camera module 143, image management module 144 includes executableinstructions to arrange, modify (e.g., edit), or otherwise manipulate,label, delete, present (e.g., in a digital slide show or album), andstore still and/or video images.

In conjunction with RF circuitry 108, touch screen 112, displaycontroller 156, contact/motion module 130, graphics module 132, and textinput module 134, browser module 147 includes executable instructions tobrowse the Internet in accordance with user instructions, includingsearching, linking to, receiving, and displaying web pages or portionsthereof, as well as attachments and other files linked to web pages.

In conjunction with RF circuitry 108, touch screen 112, displaycontroller 156, contact/motion module 130, graphics module 132, textinput module 134, e-mail client module 140, and browser module 147,calendar module 148 includes executable instructions to create, display,modify, and store calendars and data associated with calendars (e.g.,calendar entries, to-do lists, etc.) in accordance with userinstructions.

In conjunction with RF circuitry 108, touch screen 112, displaycontroller 156, contact/motion module 130, graphics module 132, textinput module 134, and browser module 147, widget modules 149 aremini-applications that are, optionally, downloaded and used by a user(e.g., weather widget 149-1, stocks widget 149-2, calculator widget149-3, alarm clock widget 149-4, and dictionary widget 149-5) or createdby the user (e.g., user-created widget 149-6). In some embodiments, awidget includes an HTML (Hypertext Markup Language) file, a CSS(Cascading Style Sheets) file, and a JavaScript file. In someembodiments, a widget includes an XML (Extensible Markup Language) fileand a JavaScript file (e.g., Yahoo! Widgets).

In conjunction with RF circuitry 108, touch screen 112, displaycontroller 156, contact/motion module 130, graphics module 132, textinput module 134, and browser module 147, the widget creator module 150are, optionally, used by a user to create widgets (e.g., turning auser-specified portion of a web page into a widget).

In conjunction with touch screen 112, display controller 156,contact/motion module 130, graphics module 132, and text input module134, search module 151 includes executable instructions to search fortext, music, sound, image, video, and/or other files in memory 102 thatmatch one or more search criteria (e.g., one or more user-specifiedsearch terms) in accordance with user instructions.

In conjunction with touch screen 112, display controller 156,contact/motion module 130, graphics module 132, audio circuitry 110,speaker 111, RF circuitry 108, and browser module 147, video and musicplayer module 152 includes executable instructions that allow the userto download and play back recorded music and other sound files stored inone or more file formats, such as MP3 or AAC files, and executableinstructions to display, present, or otherwise play back videos (e.g.,on touch screen 112 or on an external, connected display via externalport 124). In some embodiments, device 100 optionally includes thefunctionality of an MP3 player, such as an iPod (trademark of AppleInc.).

In conjunction with touch screen 112, display controller 156,contact/motion module 130, graphics module 132, and text input module134, notes module 153 includes executable instructions to create andmanage notes, to-do lists, and the like in accordance with userinstructions.

In conjunction with RF circuitry 108, touch screen 112, displaycontroller 156, contact/motion module 130, graphics module 132, textinput module 134, GPS module 135, and browser module 147, map module 154are, optionally, used to receive, display, modify, and store maps anddata associated with maps (e.g., driving directions, data on stores andother points of interest at or near a particular location, and otherlocation-based data) in accordance with user instructions.

In conjunction with touch screen 112, display controller 156,contact/motion module 130, graphics module 132, audio circuitry 110,speaker 111, RF circuitry 108, text input module 134, e-mail clientmodule 140, and browser module 147, online video module 155 includesinstructions that allow the user to access, browse, receive (e.g., bystreaming and/or download), play back (e.g., on the touch screen or onan external, connected display via external port 124), send an e-mailwith a link to a particular online video, and otherwise manage onlinevideos in one or more file formats, such as H.264. In some embodiments,instant messaging module 141, rather than e-mail client module 140, isused to send a link to a particular online video. Additional descriptionof the online video application can be found in U.S. Provisional PatentApplication No. 60/936,562, “Portable Multifunction Device, Method, andGraphical User Interface for Playing Online Videos,” filed Jun. 20,2007, and U.S. patent application Ser. No. 11/968,067, “PortableMultifunction Device, Method, and Graphical User Interface for PlayingOnline Videos,” filed Dec. 31, 2007, the contents of which are herebyincorporated by reference in their entirety.

Each of the above-identified modules and applications corresponds to aset of executable instructions for performing one or more functionsdescribed above and the methods described in this application (e.g., thecomputer-implemented methods and other information processing methodsdescribed herein). These modules (e.g., sets of instructions) need notbe implemented as separate software programs, procedures, or modules,and thus various subsets of these modules are, optionally, combined orotherwise rearranged in various embodiments. For example, video playermodule is, optionally, combined with music player module into a singlemodule (e.g., video and music player module 152, FIG. 1A). In someembodiments, memory 102 optionally stores a subset of the modules anddata structures identified above. Furthermore, memory 102 optionallystores additional modules and data structures not described above.

In some embodiments, device 100 is a device where operation of apredefined set of functions on the device is performed exclusivelythrough a touch screen and/or a touchpad. By using a touch screen and/ora touchpad as the primary input control device for operation of device100, the number of physical input control devices (such as push buttons,dials, and the like) on device 100 is, optionally, reduced.

The predefined set of functions that are performed exclusively through atouch screen and/or a touchpad optionally include navigation betweenuser interfaces. In some embodiments, the touchpad, when touched by theuser, navigates device 100 to a main, home, or root menu from any userinterface that is displayed on device 100. In such embodiments, a “menubutton” is implemented using a touchpad. In some other embodiments, themenu button is a physical push button or other physical input controldevice instead of a touchpad.

FIG. 1B is a block diagram illustrating exemplary components for eventhandling in accordance with some embodiments. In some embodiments,memory 102 (FIG. 1A) or 370 (FIG. 3) includes event sorter 170 (e.g., inoperating system 126) and a respective application 136-1 (e.g., any ofthe aforementioned applications 137-151, 155, 380-390).

Event sorter 170 receives event information and determines theapplication 136-1 and application view 191 of application 136-1 to whichto deliver the event information. Event sorter 170 includes eventmonitor 171 and event dispatcher module 174. In some embodiments,application 136-1 includes application internal state 192, whichindicates the current application view(s) displayed on touch-sensitivedisplay 112 when the application is active or executing. In someembodiments, device/global internal state 157 is used by event sorter170 to determine which application(s) is (are) currently active, andapplication internal state 192 is used by event sorter 170 to determineapplication views 191 to which to deliver event information.

In some embodiments, application internal state 192 includes additionalinformation, such as one or more of: resume information to be used whenapplication 136-1 resumes execution, user interface state informationthat indicates information being displayed or that is ready for displayby application 136-1, a state queue for enabling the user to go back toa prior state or view of application 136-1, and a redo/undo queue ofprevious actions taken by the user.

Event monitor 171 receives event information from peripherals interface118. Event information includes information about a sub-event (e.g., auser touch on touch-sensitive display 112, as part of a multi-touchgesture). Peripherals interface 118 transmits information it receivesfrom I/O subsystem 106 or a sensor, such as proximity sensor 166,accelerometer(s) 168, and/or microphone 113 (through audio circuitry110). Information that peripherals interface 118 receives from I/Osubsystem 106 includes information from touch-sensitive display 112 or atouch-sensitive surface.

In some embodiments, event monitor 171 sends requests to the peripheralsinterface 118 at predetermined intervals. In response, peripheralsinterface 118 transmits event information. In other embodiments,peripherals interface 118 transmits event information only when there isa significant event (e.g., receiving an input above a predeterminednoise threshold and/or for more than a predetermined duration).

In some embodiments, event sorter 170 also includes a hit viewdetermination module 172 and/or an active event recognizer determinationmodule 173.

Hit view determination module 172 provides software procedures fordetermining where a sub-event has taken place within one or more viewswhen touch-sensitive display 112 displays more than one view. Views aremade up of controls and other elements that a user can see on thedisplay.

Another aspect of the user interface associated with an application is aset of views, sometimes herein called application views or userinterface windows, in which information is displayed and touch-basedgestures occur. The application views (of a respective application) inwhich a touch is detected optionally correspond to programmatic levelswithin a programmatic or view hierarchy of the application. For example,the lowest level view in which a touch is detected is, optionally,called the hit view, and the set of events that are recognized as properinputs are, optionally, determined based, at least in part, on the hitview of the initial touch that begins a touch-based gesture.

Hit view determination module 172 receives information related tosub-events of a touch-based gesture. When an application has multipleviews organized in a hierarchy, hit view determination module 172identifies a hit view as the lowest view in the hierarchy which shouldhandle the sub-event. In most circumstances, the hit view is the lowestlevel view in which an initiating sub-event occurs (e.g., the firstsub-event in the sequence of sub-events that form an event or potentialevent). Once the hit view is identified by the hit view determinationmodule 172, the hit view typically receives all sub-events related tothe same touch or input source for which it was identified as the hitview.

Active event recognizer determination module 173 determines which viewor views within a view hierarchy should receive a particular sequence ofsub-events. In some embodiments, active event recognizer determinationmodule 173 determines that only the hit view should receive a particularsequence of sub-events. In other embodiments, active event recognizerdetermination module 173 determines that all views that include thephysical location of a sub-event are actively involved views, andtherefore determines that all actively involved views should receive aparticular sequence of sub-events. In other embodiments, even if touchsub-events were entirely confined to the area associated with oneparticular view, views higher in the hierarchy would still remain asactively involved views.

Event dispatcher module 174 dispatches the event information to an eventrecognizer (e.g., event recognizer 180). In embodiments including activeevent recognizer determination module 173, event dispatcher module 174delivers the event information to an event recognizer determined byactive event recognizer determination module 173. In some embodiments,event dispatcher module 174 stores in an event queue the eventinformation, which is retrieved by a respective event receiver 182.

In some embodiments, operating system 126 includes event sorter 170.Alternatively, application 136-1 includes event sorter 170. In yet otherembodiments, event sorter 170 is a stand-alone module, or a part ofanother module stored in memory 102, such as contact/motion module 130.

In some embodiments, application 136-1 includes a plurality of eventhandlers 190 and one or more application views 191, each of whichincludes instructions for handling touch events that occur within arespective view of the application's user interface. Each applicationview 191 of the application 136-1 includes one or more event recognizers180. Typically, a respective application view 191 includes a pluralityof event recognizers 180. In other embodiments, one or more of eventrecognizers 180 are part of a separate module, such as a user interfacekit or a higher level object from which application 136-1 inheritsmethods and other properties. In some embodiments, a respective eventhandler 190 includes one or more of: data updater 176, object updater177, GUI updater 178, and/or event data 179 received from event sorter170. Event handler 190 optionally utilizes or calls data updater 176,object updater 177, or GUI updater 178 to update the applicationinternal state 192. Alternatively, one or more of the application views191 include one or more respective event handlers 190. Also, in someembodiments, one or more of data updater 176, object updater 177, andGUI updater 178 are included in a respective application view 191.

A respective event recognizer 180 receives event information (e.g.,event data 179) from event sorter 170 and identifies an event from theevent information. Event recognizer 180 includes event receiver 182 andevent comparator 184. In some embodiments, event recognizer 180 alsoincludes at least a subset of: metadata 183, and event deliveryinstructions 188 (which optionally include sub-event deliveryinstructions).

Event receiver 182 receives event information from event sorter 170. Theevent information includes information about a sub-event, for example, atouch or a touch movement. Depending on the sub-event, the eventinformation also includes additional information, such as location ofthe sub-event. When the sub-event concerns motion of a touch, the eventinformation optionally also includes speed and direction of thesub-event. In some embodiments, events include rotation of the devicefrom one orientation to another (e.g., from a portrait orientation to alandscape orientation, or vice versa), and the event informationincludes corresponding information about the current orientation (alsocalled device attitude) of the device.

Event comparator 184 compares the event information to predefined eventor sub-event definitions and, based on the comparison, determines anevent or sub-event, or determines or updates the state of an event orsub-event. In some embodiments, event comparator 184 includes eventdefinitions 186. Event definitions 186 contain definitions of events(e.g., predefined sequences of sub-events), for example, event 1(187-1), event 2 (187-2), and others. In some embodiments, sub-events inan event (187) include, for example, touch begin, touch end, touchmovement, touch cancellation, and multiple touching. In one example, thedefinition for event 1 (187-1) is a double tap on a displayed object.The double tap, for example, comprises a first touch (touch begin) onthe displayed object for a predetermined phase, a first liftoff (touchend) for a predetermined phase, a second touch (touch begin) on thedisplayed object for a predetermined phase, and a second liftoff (touchend) for a predetermined phase. In another example, the definition forevent 2 (187-2) is a dragging on a displayed object. The dragging, forexample, comprises a touch (or contact) on the displayed object for apredetermined phase, a movement of the touch across touch-sensitivedisplay 112, and liftoff of the touch (touch end). In some embodiments,the event also includes information for one or more associated eventhandlers 190.

In some embodiments, event definition 187 includes a definition of anevent for a respective user-interface object. In some embodiments, eventcomparator 184 performs a hit test to determine which user-interfaceobject is associated with a sub-event. For example, in an applicationview in which three user-interface objects are displayed ontouch-sensitive display 112, when a touch is detected on touch-sensitivedisplay 112, event comparator 184 performs a hit test to determine whichof the three user-interface objects is associated with the touch(sub-event). If each displayed object is associated with a respectiveevent handler 190, the event comparator uses the result of the hit testto determine which event handler 190 should be activated. For example,event comparator 184 selects an event handler associated with thesub-event and the object triggering the hit test.

In some embodiments, the definition for a respective event (187) alsoincludes delayed actions that delay delivery of the event informationuntil after it has been determined whether the sequence of sub-eventsdoes or does not correspond to the event recognizer's event type.

When a respective event recognizer 180 determines that the series ofsub-events do not match any of the events in event definitions 186, therespective event recognizer 180 enters an event impossible, eventfailed, or event ended state, after which it disregards subsequentsub-events of the touch-based gesture. In this situation, other eventrecognizers, if any, that remain active for the hit view continue totrack and process sub-events of an ongoing touch-based gesture.

In some embodiments, a respective event recognizer 180 includes metadata183 with configurable properties, flags, and/or lists that indicate howthe event delivery system should perform sub-event delivery to activelyinvolved event recognizers. In some embodiments, metadata 183 includesconfigurable properties, flags, and/or lists that indicate how eventrecognizers interact, or are enabled to interact, with one another. Insome embodiments, metadata 183 includes configurable properties, flags,and/or lists that indicate whether sub-events are delivered to varyinglevels in the view or programmatic hierarchy.

In some embodiments, a respective event recognizer 180 activates eventhandler 190 associated with an event when one or more particularsub-events of an event are recognized. In some embodiments, a respectiveevent recognizer 180 delivers event information associated with theevent to event handler 190. Activating an event handler 190 is distinctfrom sending (and deferred sending) sub-events to a respective hit view.In some embodiments, event recognizer 180 throws a flag associated withthe recognized event, and event handler 190 associated with the flagcatches the flag and performs a predefined process.

In some embodiments, event delivery instructions 188 include sub-eventdelivery instructions that deliver event information about a sub-eventwithout activating an event handler. Instead, the sub-event deliveryinstructions deliver event information to event handlers associated withthe series of sub-events or to actively involved views. Event handlersassociated with the series of sub-events or with actively involved viewsreceive the event information and perform a predetermined process.

In some embodiments, data updater 176 creates and updates data used inapplication 136-1. For example, data updater 176 updates the telephonenumber used in contacts module 137, or stores a video file used in videoplayer module. In some embodiments, object updater 177 creates andupdates objects used in application 136-1. For example, object updater177 creates a new user-interface object or updates the position of auser-interface object. GUI updater 178 updates the GUI. For example, GUIupdater 178 prepares display information and sends it to graphics module132 for display on a touch-sensitive display.

In some embodiments, event handler(s) 190 includes or has access to dataupdater 176, object updater 177, and GUI updater 178. In someembodiments, data updater 176, object updater 177, and GUI updater 178are included in a single module of a respective application 136-1 orapplication view 191. In other embodiments, they are included in two ormore software modules.

It shall be understood that the foregoing discussion regarding eventhandling of user touches on touch-sensitive displays also applies toother forms of user inputs to operate multifunction devices 100 withinput devices, not all of which are initiated on touch screens. Forexample, mouse movement and mouse button presses, optionally coordinatedwith single or multiple keyboard presses or holds; contact movementssuch as taps, drags, scrolls, etc. on touchpads; pen stylus inputs;movement of the device; oral instructions; detected eye movements;biometric inputs; and/or any combination thereof are optionally utilizedas inputs corresponding to sub-events which define an event to berecognized.

FIG. 2 illustrates a portable multifunction device 100 having a touchscreen 112 in accordance with some embodiments. The touch screenoptionally displays one or more graphics within user interface (UI) 200.In this embodiment, as well as others described below, a user is enabledto select one or more of the graphics by making a gesture on thegraphics, for example, with one or more fingers 202 (not drawn to scalein the figure) or one or more styluses 203 (not drawn to scale in thefigure). In some embodiments, selection of one or more graphics occurswhen the user breaks contact with the one or more graphics. In someembodiments, the gesture optionally includes one or more taps, one ormore swipes (from left to right, right to left, upward and/or downward),and/or a rolling of a finger (from right to left, left to right, upwardand/or downward) that has made contact with device 100. In someimplementations or circumstances, inadvertent contact with a graphicdoes not select the graphic. For example, a swipe gesture that sweepsover an application icon optionally does not select the correspondingapplication when the gesture corresponding to selection is a tap.

Device 100 optionally also include one or more physical buttons, such as“home” or menu button 204. As described previously, menu button 204 is,optionally, used to navigate to any application 136 in a set ofapplications that are, optionally, executed on device 100.Alternatively, in some embodiments, the menu button is implemented as asoft key in a GUI displayed on touch screen 112.

In some embodiments, device 100 includes touch screen 112, menu button204, push button 206 for powering the device on/off and locking thedevice, volume adjustment button(s) 208, subscriber identity module(SIM) card slot 210, headset jack 212, and docking/charging externalport 124. Push button 206 is, optionally, used to turn the power on/offon the device by depressing the button and holding the button in thedepressed state for a predefined time interval; to lock the device bydepressing the button and releasing the button before the predefinedtime interval has elapsed; and/or to unlock the device or initiate anunlock process. In an alternative embodiment, device 100 also acceptsverbal input for activation or deactivation of some functions throughmicrophone 113. Device 100 also, optionally, includes one or morecontact intensity sensors 165 for detecting intensity of contacts ontouch screen 112 and/or one or more tactile output generators 167 forgenerating tactile outputs for a user of device 100.

FIG. 3 is a block diagram of an exemplary multifunction device with adisplay and a touch-sensitive surface in accordance with someembodiments. Device 300 need not be portable. In some embodiments,device 300 is a laptop computer, a desktop computer, a tablet computer,a multimedia player device, a navigation device, an educational device(such as a child's learning toy), a gaming system, or a control device(e.g., a home or industrial controller). Device 300 typically includesone or more processing units (CPUs) 310, one or more network or othercommunications interfaces 360, memory 370, and one or more communicationbuses 320 for interconnecting these components. Communication buses 320optionally include circuitry (sometimes called a chipset) thatinterconnects and controls communications between system components.Device 300 includes input/output (I/O) interface 330 comprising display340, which is typically a touch screen display. I/O interface 330 alsooptionally includes a keyboard and/or mouse (or other pointing device)350 and touchpad 355, tactile output generator 357 for generatingtactile outputs on device 300 (e.g., similar to tactile outputgenerator(s) 167 described above with reference to FIG. 1A), sensors 359(e.g., optical, acceleration, proximity, touch-sensitive, and/or contactintensity sensors similar to contact intensity sensor(s) 165 describedabove with reference to FIG. 1A). Memory 370 includes high-speed randomaccess memory, such as DRAM, SRAM, DDR RAM, or other random access solidstate memory devices; and optionally includes non-volatile memory, suchas one or more magnetic disk storage devices, optical disk storagedevices, flash memory devices, or other non-volatile solid state storagedevices. Memory 370 optionally includes one or more storage devicesremotely located from CPU(s) 310. In some embodiments, memory 370 storesprograms, modules, and data structures analogous to the programs,modules, and data structures stored in memory 102 of portablemultifunction device 100 (FIG. 1A), or a subset thereof. Furthermore,memory 370 optionally stores additional programs, modules, and datastructures not present in memory 102 of portable multifunction device100. For example, memory 370 of device 300 optionally stores drawingmodule 380, presentation module 382, word processing module 384, websitecreation module 386, disk authoring module 388, and/or spreadsheetmodule 390, while memory 102 of portable multifunction device 100 (FIG.1A) optionally does not store these modules.

Each of the above-identified elements in FIG. 3 is, optionally, storedin one or more of the previously mentioned memory devices. Each of theabove-identified modules corresponds to a set of instructions forperforming a function described above. The above-identified modules orprograms (e.g., sets of instructions) need not be implemented asseparate software programs, procedures, or modules, and thus varioussubsets of these modules are, optionally, combined or otherwiserearranged in various embodiments. In some embodiments, memory 370optionally stores a subset of the modules and data structures identifiedabove. Furthermore, memory 370 optionally stores additional modules anddata structures not described above.

Attention is now directed towards embodiments of user interfaces thatare, optionally, implemented on, for example, portable multifunctiondevice 100.

FIG. 4A illustrates an exemplary user interface for a menu ofapplications on portable multifunction device 100 in accordance withsome embodiments. Similar user interfaces are, optionally, implementedon device 300. In some embodiments, user interface 400 includes thefollowing elements, or a subset or superset thereof:

-   -   Signal strength indicator(s) 402 for wireless communication(s),        such as cellular and Wi-Fi signals;    -   Time 404;    -   Bluetooth indicator 405;    -   Battery status indicator 406;    -   Tray 408 with icons for frequently used applications, such as:        -   Icon 416 for telephone module 138, labeled “Phone,” which            optionally includes an indicator 414 of the number of missed            calls or voicemail messages;        -   Icon 418 for e-mail client module 140, labeled “Mail,” which            optionally includes an indicator 410 of the number of unread            e-mails;        -   Icon 420 for browser module 147, labeled “Browser;” and        -   Icon 422 for video and music player module 152, also            referred to as iPod (trademark of Apple Inc.) module 152,            labeled “iPod;” and    -   Icons for other applications, such as:        -   Icon 424 for IM module 141, labeled “Messages;”        -   Icon 426 for calendar module 148, labeled “Calendar;”        -   Icon 428 for image management module 144, labeled “Photos;”        -   Icon 430 for camera module 143, labeled “Camera;”        -   Icon 432 for online video module 155, labeled “Online            Video;”        -   Icon 434 for stocks widget 149-2, labeled “Stocks;”        -   Icon 436 for map module 154, labeled “Maps;”        -   Icon 438 for weather widget 149-1, labeled “Weather;”        -   Icon 440 for alarm clock widget 149-4, labeled “Clock;”        -   Icon 442 for workout support module 142, labeled “Workout            Support;”        -   Icon 444 for notes module 153, labeled “Notes;” and        -   Icon 446 for a settings application or module, labeled            “Settings,” which provides access to settings for device 100            and its various applications 136.

It should be noted that the icon labels illustrated in FIG. 4A aremerely exemplary. For example, icon 422 for video and music playermodule 152 is labeled “Music” or “Music Player.” Other labels are,optionally, used for various application icons. In some embodiments, alabel for a respective application icon includes a name of anapplication corresponding to the respective application icon. In someembodiments, a label for a particular application icon is distinct froma name of an application corresponding to the particular applicationicon.

FIG. 4B illustrates an exemplary user interface on a device (e.g.,device 300, FIG. 3) with a touch-sensitive surface 451 (e.g., a tabletor touchpad 355, FIG. 3) that is separate from the display 450 (e.g.,touch screen display 112). Device 300 also, optionally, includes one ormore contact intensity sensors (e.g., one or more of sensors 359) fordetecting intensity of contacts on touch-sensitive surface 451 and/orone or more tactile output generators 357 for generating tactile outputsfor a user of device 300.

Although some of the examples that follow will be given with referenceto inputs on touch screen display 112 (where the touch-sensitive surfaceand the display are combined), in some embodiments, the device detectsinputs on a touch-sensitive surface that is separate from the display,as shown in FIG. 4B. In some embodiments, the touch-sensitive surface(e.g., 451 in FIG. 4B) has a primary axis (e.g., 452 in FIG. 4B) thatcorresponds to a primary axis (e.g., 453 in FIG. 4B) on the display(e.g., 450). In accordance with these embodiments, the device detectscontacts (e.g., 460 and 462 in FIG. 4B) with the touch-sensitive surface451 at locations that correspond to respective locations on the display(e.g., in FIG. 4B, 460 corresponds to 468 and 462 corresponds to 470).In this way, user inputs (e.g., contacts 460 and 462, and movementsthereof) detected by the device on the touch-sensitive surface (e.g.,451 in FIG. 4B) are used by the device to manipulate the user interfaceon the display (e.g., 450 in FIG. 4B) of the multifunction device whenthe touch-sensitive surface is separate from the display. It should beunderstood that similar methods are, optionally, used for other userinterfaces described herein.

Additionally, while the following examples are given primarily withreference to finger inputs (e.g., finger contacts, finger tap gestures,finger swipe gestures), it should be understood that, in someembodiments, one or more of the finger inputs are replaced with inputfrom another input device (e.g., a mouse-based input or stylus input).For example, a swipe gesture is, optionally, replaced with a mouse click(e.g., instead of a contact) followed by movement of the cursor alongthe path of the swipe (e.g., instead of movement of the contact). Asanother example, a tap gesture is, optionally, replaced with a mouseclick while the cursor is located over the location of the tap gesture(e.g., instead of detection of the contact followed by ceasing to detectthe contact). Similarly, when multiple user inputs are simultaneouslydetected, it should be understood that multiple computer mice are,optionally, used simultaneously, or a mouse and finger contacts are,optionally, used simultaneously.

FIG. 5A illustrates exemplary personal electronic device 500. Device 500includes body 502. In some embodiments, device 500 can include some orall of the features described with respect to devices 100 and 300 (e.g.,FIGS. 1A-4B). In some embodiments, device 500 has touch-sensitivedisplay screen 504, hereafter touch screen 504. Alternatively, or inaddition to touch screen 504, device 500 has a display and atouch-sensitive surface. As with devices 100 and 300, in someembodiments, touch screen 504 (or the touch-sensitive surface)optionally includes one or more intensity sensors for detectingintensity of contacts (e.g., touches) being applied. The one or moreintensity sensors of touch screen 504 (or the touch-sensitive surface)can provide output data that represents the intensity of touches. Theuser interface of device 500 can respond to touches based on theirintensity, meaning that touches of different intensities can invokedifferent user interface operations on device 500.

Exemplary techniques for detecting and processing touch intensity arefound, for example, in related applications: International PatentApplication Serial No. PCT/US2013/040061, titled “Device, Method, andGraphical User Interface for Displaying User Interface ObjectsCorresponding to an Application,” filed May 8, 2013, published as WIPOPublication No. WO/2013/169849, and International Patent ApplicationSerial No. PCT/US2013/069483, titled “Device, Method, and Graphical UserInterface for Transitioning Between Touch Input to Display OutputRelationships,” filed Nov. 11, 2013, published as WIPO Publication No.WO/2014/105276, each of which is hereby incorporated by reference intheir entirety.

In some embodiments, device 500 has one or more input mechanisms 506 and508. Input mechanisms 506 and 508, if included, can be physical.Examples of physical input mechanisms include push buttons and rotatablemechanisms. In some embodiments, device 500 has one or more attachmentmechanisms. Such attachment mechanisms, if included, can permitattachment of device 500 with, for example, hats, eyewear, earrings,necklaces, shirts, jackets, bracelets, watch straps, chains, trousers,belts, shoes, purses, backpacks, and so forth. These attachmentmechanisms permit device 500 to be worn by a user.

FIG. 5B depicts exemplary personal electronic device 500. In someembodiments, device 500 can include some or all of the componentsdescribed with respect to FIGS. 1A, 1B, and 3. Device 500 has bus 512that operatively couples I/O section 514 with one or more computerprocessors 516 and memory 518. I/O section 514 can be connected todisplay 504, which can have touch-sensitive component 522 and,optionally, intensity sensor 524 (e.g., contact intensity sensor). Inaddition, I/O section 514 can be connected with communication unit 530for receiving application and operating system data, using Wi-Fi,Bluetooth, near field communication (NFC), cellular, and/or otherwireless communication techniques. Device 500 can include inputmechanisms 506 and/or 508. Input mechanism 506 is, optionally, arotatable input device or a depressible and rotatable input device, forexample. Input mechanism 508 is, optionally, a button, in some examples.

Input mechanism 508 is, optionally, a microphone, in some examples.Personal electronic device 500 optionally includes various sensors, suchas GPS sensor 532, accelerometer 534, directional sensor 540 (e.g.,compass), gyroscope 536, motion sensor 538, and/or a combinationthereof, all of which can be operatively connected to I/O section 514.

Memory 518 of personal electronic device 500 can include one or morenon-transitory computer-readable storage mediums, for storingcomputer-executable instructions, which, when executed by one or morecomputer processors 516, for example, can cause the computer processorsto perform the techniques described below, including process 700 (FIGS.7A-7F). A computer-readable storage medium can be any medium that cantangibly contain or store computer-executable instructions for use by orin connection with the instruction execution system, apparatus, ordevice. In some examples, the storage medium is a transitorycomputer-readable storage medium. In some examples, the storage mediumis a non-transitory computer-readable storage medium. The non-transitorycomputer-readable storage medium can include, but is not limited to,magnetic, optical, and/or semiconductor storages. Examples of suchstorage include magnetic disks, optical discs based on CD, DVD, orBlu-ray technologies, as well as persistent solid-state memory such asflash, solid-state drives, and the like. Personal electronic device 500is not limited to the components and configuration of FIG. 5B, but caninclude other or additional components in multiple configurations.

As used here, the term “affordance” refers to a user-interactivegraphical user interface object that is, optionally, displayed on thedisplay screen of devices 100, 300, and/or 500 (FIGS. 1A, 3, and 5A-5B).For example, an image (e.g., icon), a button, and text (e.g., hyperlink)each optionally constitute an affordance.

As used herein, the term “focus selector” refers to an input elementthat indicates a current part of a user interface with which a user isinteracting. In some implementations that include a cursor or otherlocation marker, the cursor acts as a “focus selector” so that when aninput (e.g., a press input) is detected on a touch-sensitive surface(e.g., touchpad 355 in FIG. 3 or touch-sensitive surface 451 in FIG. 4B)while the cursor is over a particular user interface element (e.g., abutton, window, slider, or other user interface element), the particularuser interface element is adjusted in accordance with the detectedinput. In some implementations that include a touch screen display(e.g., touch-sensitive display system 112 in FIG. 1A or touch screen 112in FIG. 4A) that enables direct interaction with user interface elementson the touch screen display, a detected contact on the touch screen actsas a “focus selector” so that when an input (e.g., a press input by thecontact) is detected on the touch screen display at a location of aparticular user interface element (e.g., a button, window, slider, orother user interface element), the particular user interface element isadjusted in accordance with the detected input. In some implementations,focus is moved from one region of a user interface to another region ofthe user interface without corresponding movement of a cursor ormovement of a contact on a touch screen display (e.g., by using a tabkey or arrow keys to move focus from one button to another button); inthese implementations, the focus selector moves in accordance withmovement of focus between different regions of the user interface.Without regard to the specific form taken by the focus selector, thefocus selector is generally the user interface element (or contact on atouch screen display) that is controlled by the user so as tocommunicate the user's intended interaction with the user interface(e.g., by indicating, to the device, the element of the user interfacewith which the user is intending to interact). For example, the locationof a focus selector (e.g., a cursor, a contact, or a selection box) overa respective button while a press input is detected on thetouch-sensitive surface (e.g., a touchpad or touch screen) will indicatethat the user is intending to activate the respective button (as opposedto other user interface elements shown on a display of the device).

As used in the specification and claims, the term “characteristicintensity” of a contact refers to a characteristic of the contact basedon one or more intensities of the contact. In some embodiments, thecharacteristic intensity is based on multiple intensity samples. Thecharacteristic intensity is, optionally, based on a predefined number ofintensity samples, or a set of intensity samples collected during apredetermined time period (e.g., 0.05, 0.1, 0.2, 0.5, 1, 2, 5, 10seconds) relative to a predefined event (e.g., after detecting thecontact, prior to detecting liftoff of the contact, before or afterdetecting a start of movement of the contact, prior to detecting an endof the contact, before or after detecting an increase in intensity ofthe contact, and/or before or after detecting a decrease in intensity ofthe contact). A characteristic intensity of a contact is, optionally,based on one or more of: a maximum value of the intensities of thecontact, a mean value of the intensities of the contact, an averagevalue of the intensities of the contact, a top 10 percentile value ofthe intensities of the contact, a value at the half maximum of theintensities of the contact, a value at the 90 percent maximum of theintensities of the contact, or the like. In some embodiments, theduration of the contact is used in determining the characteristicintensity (e.g., when the characteristic intensity is an average of theintensity of the contact over time). In some embodiments, thecharacteristic intensity is compared to a set of one or more intensitythresholds to determine whether an operation has been performed by auser. For example, the set of one or more intensity thresholdsoptionally includes a first intensity threshold and a second intensitythreshold. In this example, a contact with a characteristic intensitythat does not exceed the first threshold results in a first operation, acontact with a characteristic intensity that exceeds the first intensitythreshold and does not exceed the second intensity threshold results ina second operation, and a contact with a characteristic intensity thatexceeds the second threshold results in a third operation. In someembodiments, a comparison between the characteristic intensity and oneor more thresholds is used to determine whether or not to perform one ormore operations (e.g., whether to perform a respective operation orforgo performing the respective operation), rather than being used todetermine whether to perform a first operation or a second operation.

In some embodiments, a portion of a gesture is identified for purposesof determining a characteristic intensity. For example, atouch-sensitive surface optionally receives a continuous swipe contacttransitioning from a start location and reaching an end location, atwhich point the intensity of the contact increases. In this example, thecharacteristic intensity of the contact at the end location is,optionally, based on only a portion of the continuous swipe contact, andnot the entire swipe contact (e.g., only the portion of the swipecontact at the end location). In some embodiments, a smoothing algorithmis, optionally, applied to the intensities of the swipe contact prior todetermining the characteristic intensity of the contact. For example,the smoothing algorithm optionally includes one or more of: anunweighted sliding-average smoothing algorithm, a triangular smoothingalgorithm, a median filter smoothing algorithm, and/or an exponentialsmoothing algorithm. In some circumstances, these smoothing algorithmseliminate narrow spikes or dips in the intensities of the swipe contactfor purposes of determining a characteristic intensity.

The intensity of a contact on the touch-sensitive surface is,optionally, characterized relative to one or more intensity thresholds,such as a contact-detection intensity threshold, a light press intensitythreshold, a deep press intensity threshold, and/or one or more otherintensity thresholds. In some embodiments, the light press intensitythreshold corresponds to an intensity at which the device will performoperations typically associated with clicking a button of a physicalmouse or a trackpad. In some embodiments, the deep press intensitythreshold corresponds to an intensity at which the device will performoperations that are different from operations typically associated withclicking a button of a physical mouse or a trackpad. In someembodiments, when a contact is detected with a characteristic intensitybelow the light press intensity threshold (e.g., and above a nominalcontact-detection intensity threshold below which the contact is nolonger detected), the device will move a focus selector in accordancewith movement of the contact on the touch-sensitive surface withoutperforming an operation associated with the light press intensitythreshold or the deep press intensity threshold. Generally, unlessotherwise stated, these intensity thresholds are consistent betweendifferent sets of user interface figures.

An increase of characteristic intensity of the contact from an intensitybelow the light press intensity threshold to an intensity between thelight press intensity threshold and the deep press intensity thresholdis sometimes referred to as a “light press” input. An increase ofcharacteristic intensity of the contact from an intensity below the deeppress intensity threshold to an intensity above the deep press intensitythreshold is sometimes referred to as a “deep press” input. An increaseof characteristic intensity of the contact from an intensity below thecontact-detection intensity threshold to an intensity between thecontact-detection intensity threshold and the light press intensitythreshold is sometimes referred to as detecting the contact on thetouch-surface. A decrease of characteristic intensity of the contactfrom an intensity above the contact-detection intensity threshold to anintensity below the contact-detection intensity threshold is sometimesreferred to as detecting liftoff of the contact from the touch-surface.In some embodiments, the contact-detection intensity threshold is zero.In some embodiments, the contact-detection intensity threshold isgreater than zero.

In some embodiments described herein, one or more operations areperformed in response to detecting a gesture that includes a respectivepress input or in response to detecting the respective press inputperformed with a respective contact (or a plurality of contacts), wherethe respective press input is detected based at least in part ondetecting an increase in intensity of the contact (or plurality ofcontacts) above a press-input intensity threshold. In some embodiments,the respective operation is performed in response to detecting theincrease in intensity of the respective contact above the press-inputintensity threshold (e.g., a “down stroke” of the respective pressinput). In some embodiments, the press input includes an increase inintensity of the respective contact above the press-input intensitythreshold and a subsequent decrease in intensity of the contact belowthe press-input intensity threshold, and the respective operation isperformed in response to detecting the subsequent decrease in intensityof the respective contact below the press-input threshold (e.g., an “upstroke” of the respective press

In some embodiments, the device employs intensity hysteresis to avoidaccidental inputs sometimes termed “jitter,” where the device defines orselects a hysteresis intensity threshold with a predefined relationshipto the press-input intensity threshold (e.g., the hysteresis intensitythreshold is X intensity units lower than the press-input intensitythreshold or the hysteresis intensity threshold is 75%, 90%, or somereasonable proportion of the press-input intensity threshold). Thus, insome embodiments, the press input includes an increase in intensity ofthe respective contact above the press-input intensity threshold and asubsequent decrease in intensity of the contact below the hysteresisintensity threshold that corresponds to the press-input intensitythreshold, and the respective operation is performed in response todetecting the subsequent decrease in intensity of the respective contactbelow the hysteresis intensity threshold (e.g., an “up stroke” of therespective press input). Similarly, in some embodiments, the press inputis detected only when the device detects an increase in intensity of thecontact from an intensity at or below the hysteresis intensity thresholdto an intensity at or above the press-input intensity threshold and,optionally, a subsequent decrease in intensity of the contact to anintensity at or below the hysteresis intensity, and the respectiveoperation is performed in response to detecting the press input (e.g.,the increase in intensity of the contact or the decrease in intensity ofthe contact, depending on the circumstances).

For ease of explanation, the descriptions of operations performed inresponse to a press input associated with a press-input intensitythreshold or in response to a gesture including the press input are,optionally, triggered in response to detecting either: an increase inintensity of a contact above the press-input intensity threshold, anincrease in intensity of a contact from an intensity below thehysteresis intensity threshold to an intensity above the press-inputintensity threshold, a decrease in intensity of the contact below thepress-input intensity threshold, and/or a decrease in intensity of thecontact below the hysteresis intensity threshold corresponding to thepress-input intensity threshold. Additionally, in examples where anoperation is described as being performed in response to detecting adecrease in intensity of a contact below the press-input intensitythreshold, the operation is, optionally, performed in response todetecting a decrease in intensity of the contact below a hysteresisintensity threshold corresponding to, and lower than, the press-inputintensity threshold.

As used herein, an “installed application” refers to a softwareapplication that has been downloaded onto an electronic device (e.g.,devices 100, 300, and/or 500) and is ready to be launched (e.g., becomeopened) on the device. In some embodiments, a downloaded applicationbecomes an installed application by way of an installation program thatextracts program portions from a downloaded package and integrates theextracted portions with the operating system of the computer system.

Attention is now directed towards embodiments of user interfaces (“UI”)and associated processes that are implemented on an electronic device,such as portable multifunction device 100, device 300, or device 500.

FIGS. 6A-6AB illustrate exemplary user interfaces for managing userinterface sharing using a computer system (e.g., 600A, 600B, 600C, 600D;an electronic device, such as a smartphone or smartwatch), in accordancewith some embodiments. The user interfaces in these figures are used toillustrate the processes described below, including the processes inFIGS. 7A-7F.

FIG. 6A illustrates a computer system 600A (e.g., a smartphone) and acomputer system 600B (e.g., a smartwatch). In some embodiments, computersystem 600A is paired with computer system 600B. In some embodiments,computer system 600A can be used to control and/or manage configurationsand settings on computer system 600B (e.g., via a companion applicationfor computer system 600B that is accessible on computer system 600A).

FIG. 6A illustrates a method for downloading the first user interfacetemplate on a computer system (e.g., computer system 600A or 600B) froma link (e.g., a hyperlink).

In FIG. 6A, computer system 600A displays, via a display generationcomponent 602A, a user interface 604A of a browser application (e.g., aweb browser), where user interface 604A is showing a webpage 606A fordownloading a first user interface template onto a respective computersystem (e.g., a respective electronic device). In some embodiments, thefirst user interface template corresponds to a user interface thatincludes one or more user interface elements that correspond to one ormore respective applications. In some embodiments, the first userinterface template corresponds to a user interface that can be used as awatch user interface (e.g., a watch face) on an electronic device (e.g.,a smartwatch), where the watch user interface includes one or more watchcomplications (e.g., also referred to as “complications”) thatcorrespond to one or more respective applications, as will be describedin greater detail below with reference to FIG. 6F.

In some embodiments, a complication refers to any clock face featureother than those used to indicate the hours and minutes of a time (e.g.,clock hands or hour/minute indications). In some embodiments,complications provide data obtained from an application. In someembodiments, a complication includes an affordance that when selectedlaunches a corresponding application. In some embodiments, acomplication is displayed at a fixed, predefined location on thedisplay. In some embodiments, complications occupy respective locationsat particular regions of a watch face (e.g., lower-right, lower-left,upper-right, and/or upper-left).

In some embodiments, the first user interface template corresponds to auser interface that can be used as a background user interface on anelectronic device (e.g., a mobile device; a smartwatch; a smartphone; atablet).

In FIG. 6A, webpage 606A includes a representation 608A (e.g., apreview) of the first user interface template and an affordance 610A(e.g., a hyperlink; a selectable user interface object; an activatableuser interface object) for initiating the downloading of the first userinterface template onto the respective computer system (e.g., ontocomputer system 600B).

Similarly, in FIG. 6A, computer system 600B displays, via a displaygeneration component 602B, a user interface 604B of a browserapplication (e.g., a web browser), where user interface 604B isdisplaying webpage 606B that corresponds to webpage 606A displayed oncomputer system 600A, and where webpage 606B includes a representation608B (e.g., a preview) of the first user interface template and anaffordance 610B (e.g., a hyperlink; a selectable user interface object;an activatable user interface object) for initiating the downloading ofthe first user interface template onto computer system 600B.

In FIG. 6A, while displaying webpage 606A, computer system 600A receives(e.g., detects) an input 601A directed to affordance 601A. In someembodiments, input 601S is a touch input on display generation component602A. In response to detecting input 601A on affordance 610A, computersystem 600A displays, via display generation component 602A, a userinterface 632A for customizing the user interface corresponding to thedownloaded first user interface template, as shown in FIG. 6F (e.g.,such that the first user interface template can be used to create a userinterface that can be used (e.g., as a watch user interface).

Similarly, while displaying webpage 606B, computer system 600B receives(e.g., detects) an input 601B on affordance 610B. In some embodiments,input 601B is a touch input on display generation component 602B. Inresponse to detecting input 601B on affordance 610B, computer system600B displays, via display generation component 602B, a user interface632B for customizing the user interface corresponding to the first userinterface template downloaded on computer system 600B, as shown in FIG.6F.

FIG. 6B illustrates a method for downloading the first user interfacetemplate on a computer system (e.g., computer system 600A or 600B) froman application store.

In FIG. 6B, computer system 600A displays, via display generationcomponent 602A, a user interface 6100A of an application store. In someembodiments, the application store includes a page (e.g., a “TODAY”page; a tab) that shows one or more user interface templates that areavailable for download. In some embodiments, the first user interfacetemplate can be downloaded from the application store. In FIG. 6B, userinterface 6100A of the application store includes a user interfaceelement 6102A (e.g., a platter) (e.g., including a representation of thefirst user interface template) indicating that the first user interfacetemplate can be downloaded, and an affordance 6104A corresponding touser interface element 6102A for downloading the first user interfacetemplate.

While displaying affordance 6104A, computer system 600A receives (e.g.,detects) an input 6101A on affordance 6104A. In response to detectinginput 6101A on affordance 6104A, computer system 600A initiates aprocess for downloading the first user interface template. In someembodiments, in response to (e.g., or while) downloading the first userinterface template, computer system 600A displays, via displaygeneration component 602A, user interface 632A for customizing the userinterface corresponding to the downloaded first user interface template,as shown in FIG. 6F.

Similarly, in FIG. 6B, computer system 600B displays, via displaygeneration component 602B, a user interface 6100B of the applicationstore, where user interface 6100A of the application store includes auser interface element 6102B (e.g., a platter) indicating that the firstuser interface template can be downloaded, and an affordance 6104B fordownloading the first user interface template on computer system 600B.

While displaying affordance 6104B, computer system 600B receives (e.g.,detects) an input 6101B on affordance 6104B. In response to detectinginput 6101B on affordance 6104B, computer system 600B initiates aprocess for downloading the first user interface template. In someembodiments, in response to (e.g., or while) downloading the first userinterface template, computer system 600B displays, via displaygeneration component 602B, user interface 632B for customizing the userinterface corresponding to the first user interface template downloadedon computer system 600B, as shown in FIG. 6F.

In some embodiments, prior to initiating the process for downloading thefirst user interface template, the computer system (e.g., computersystem 600A or 600B) requests authorization to download the first userinterface template. In some embodiments, the authorization includesbiometric authentication (e.g., facial recognition authentication;fingerprint authentication; iris/retina scan authentication). In someembodiments, the authorization includes password or passcodeauthentication. In some embodiments, the authorization includesconfirmation via a user input on a mechanical input device (e.g., ahardware button) of the computer system.

As discussed in greater detail below with reference to FIGS. 6F-6G,first user interface template includes one or more complications thatrequire corresponding applications to be installed on a respectivecomputer system for a user interface (e.g., a watch user interface)created from first user interface template for use on the respectivecomputer system. In some embodiments, if one or more of the requiredapplications is not installed on the respective computer when the firstuser interface template is downloaded from the application store as inFIG. 6B, the computer system (e.g., computer system 600A or 600B)downloads the missing application(s) with the first user interfacetemplate (e.g., concurrently downloads the missing application(s) withand/or immediately after downloading the first user interface template).In some embodiments, the authorization requested to download the firstuser interface template also authorizes the downloading of the missingapplication(s) (e.g., thus, the computer system requests a singleauthorization (e.g., biometric authentication; password or passcodeauthentication) to download the first use interface template and themissing application(s)).

FIG. 6C illustrates a method for receiving the first user interfacetemplate from a contactless wireless terminal (e.g., a NFC terminal) tobe stored on a computer system (e.g., computer system 600A or 600B).

In FIG. 6C, computer system 600A receives (e.g., via NFC), from acontactless wireless terminal 612 (e.g., also referred to as a NFCterminal 612), the first user interface template. In some embodiments,in response to receiving the first user interface template from NFCterminal 612, computer system 600A displays, via display generationcomponent 602A, a preview 614A of the first user interface template andan affordance 616A for storing the first user interface template oncomputer system 600A and/or causing the first user interface template tobe stored on the respective computer system (e.g., computer system600B).

Similarly, in FIG. 6C, computer system 600B receives (e.g., via NFC),from NFC terminal 612, the first user interface template. In someembodiments, in response to receiving the first user interface templatefrom NFC terminal 612, computer system 600B displays, via displaygeneration component 602B, a preview 614B (of the first user interfacetemplate and an affordance 616B for storing the first user interfacetemplate on computer system 600B.

In FIG. 6C, while displaying affordance 616A, computer system 600Areceives (e.g., detects) an input 603A on affordance 616A. In someembodiments, input 603A is a touch input on display generation component602A. In response to receiving input 603A on affordance 616A, computersystem 600A displays, via display generation component 602A, userinterface 632A for creating a user interface (e.g., a watch userinterface) from the first user interface template for use on therespective computer system (e.g., on computer system 600B), as shown inFIG. 6F.

Similarly, in FIG. 6C, while displaying affordance 616B, computer system600B receives (e.g., detects) an input 603B on affordance 616B. In someembodiments, input 603B is a touch input on display generation component602B. In response to receiving input 603B on affordance 616B, computersystem 600B displays, via display generation component 602B, userinterface 632B for creating a user interface (e.g., a watch userinterface) from the first user interface template for use on computersystem 600B, as shown in FIG. 6F.

FIG. 6D illustrates a method for receiving (e.g., detecting) the firstuser interface template via a QR code to be stored on a computer system(e.g., on computer system 600A or 600B).

In FIG. 6D, computer system 600A detects (e.g., via one or more camerasof computer system 600A) a QR code 618. In some embodiments, in responseto detecting QR code 618, computer system 600A displays, via displaygeneration component 602A, a preview 620A of the first user interfacetemplate that has been detected from QR code 618 and an affordance 622Afor storing the first user interface template on computer system 600Aand/or causing the detected first user interface template to be storedon the respective computer system (e.g., on computer system 600B).

Similarly, in FIG. 6D, computer system 600B detects (e.g., via one ormore cameras of computer system 600B) QR code 618. In some embodiments,in response to detecting QR code 618, computer system 600B displays, viadisplay generation component 602B, a preview 620B of the first userinterface template that has been detected from QR code 618 and anaffordance 622B for storing the first user interface template oncomputer system 600B.

In FIG. 6D, while displaying affordance 622A, computer system 600Areceives (e.g., detects) an input 605A on affordance 622A. In someembodiments, input 605A is a touch input on display generation component602A. In response to receiving input 605A on affordance 622A, computersystem 600A displays, via display generation component 602A, userinterface 632A for creating a user interface (e.g., a watch userinterface) from the first user interface template for use on therespective computer system (e.g., on computer system 600B), as shown inFIG. 6F.

Similarly, in FIG. 6D, while displaying affordance 622B, computer system600B receives (e.g., detects) an input 605B on affordance 622B. Inresponse to detecting input 605B on affordance 622B, computer system600B displays, via display generation component 602B, user interface632B for creating a user interface (e.g., a watch user interface) fromthe first user interface template to be used on computer system 600B, asshown in FIG. 6F.

FIG. 6E illustrates a method for receiving the first user interfacetemplate via a messaging application.

In FIG. 6E, computer system 600A displays, via display generationcomponent 602A, a user interface 624A of a messaging application (e.g.,a text messaging application; a chat application; an electronic mailapplication), where user interface 624A of the messaging application isdisplaying a message conversation 626A with a message participant (e.g.,“Jane Appleseed”), and where message conversation 626A includes areceived electronic communication that includes (e.g., as an attachment)the first user interface template (e.g., shown as preview 628A inmessage conversation 626A) and a message 630A associated with the firstuser interface template (e.g., a message from the message participantthat was received as part of the electronic communication that includesthe first user interface template).

Similarly, in FIG. 6E, computer system 600A displays, via displaygeneration component 602A, a user interface 624B of the messagingapplication, where user interface 624A of the messaging application isdisplaying a message conversation 626B with the message participant(e.g., “Jane Appleseed”), and where message conversation 626A includes areceived electronic communication that includes (e.g., as an attachment)the first user interface template (e.g., shown as preview 628B inmessage conversation 626B) and a message 630B associated with the firstuser interface template (e.g., a message from the message participantthat was received as part of the electronic communication that includesthe first user interface template).

In FIG. 6E, while displaying message conversation 626A, computer system600A receives (e.g., detects) an input 607A directed to downloading andstoring the first user interface template. In some embodiments, input607A is a touch input (e.g., or a press-and-hold input) on preview 628A,as in FIG. 6E. In some embodiments, input 607A is a touch input on adownload affordance associated with the electronic communication. Inresponse to (e.g., or subsequent to) receiving input 607A, computersystem 600A displays, via display generation component 602A, userinterface 632A for creating a user interface (e.g., a watch userinterface) from the first user interface template to be used on therespective computer system (e.g., on computer system 600B), as shown inFIG. 6F.

Similarly, in FIG. 6E, while displaying message conversation 626B,computer system 600B receives (e.g., detects) an input 607B directed todownloading and storing the first user interface template on computersystem 600B. In some embodiments, input 607B is a touch input (e.g., ora press-and-hold input) on preview 628B, as in FIG. 6E. In someembodiments, input 607B is a touch input on a download affordanceassociated with the electronic communication. In response to (e.g., orsubsequent to) receiving input 607B, computer system 600B displays, viadisplay generation component 602B, user interface 632B for creating auser interface (e.g., a watch user interface) from the first userinterface template to be used on computer system 600B, as shown in FIG.6F.

FIG. 6F illustrates computer system 600A displaying user interface 632Afor creating a user interface (e.g., a watch user interface) from thefirst user interface template to be used on the respective computersystem (e.g., on computer system 600B) and computer system 600Bdisplaying the corresponding user interface 632B for creating a userinterface (e.g., a watch user interface) from the first user interfacetemplate to be used on computer system 600B. In some embodiments, as isthe case in FIGS. 6A-6AB, the first user interface template is a watchuser interface (e.g., a watch face) that can be used on a type ofcomputer system (e.g., a smartwatch), where the watch user interfaceincludes one or more complications that correspond to respectiveapplications, and where a respective application needs to be installedon the respective computer system in order for a correspondingcomplication to be used in the computer system through the watch userinterface.

In FIG. 6F, in response to (e.g., or subsequent to) downloading,receiving, and/or detecting the first user interface template (e.g., asdescribed above with reference to FIGS. 6A-6E), computer system 600Adisplays, via display generation component 602A, user interface 632A,where user interface 632A includes a preview 634A of the first userinterface template.

In FIG. 6F, the respective computer system for which the user interfacecorresponding to the first user interface template will be used (e.g.,computer system 600B) includes (e.g., has already installed) respectiveapplications corresponding to all of the complications that are includedwith the first user interface template (e.g., all of the respectiveapplications are already installed on and thus available on computersystem 600B). Thus, no additional applications need to be downloaded andinstalled on the respective computer system (e.g., computer system 600B)for all complications of the first user interface template to be used.

As shown in FIG. 6F, user interface 632A includes a plurality ofcomplication previews 636A, 638A, 640A, 642A, 644A, 646A, 648A, and650A. Because all of the respective applications are already installedon, and thus are available on, the respective computer system (e.g.,computer system 600B), all of complication previews 636A-650A correspondto respective complications for available applications, and computersystem 600A does not visually indicate (e.g., does not highlight) any ofcomplication previews 636A-650A (e.g., as computer system 600A (e.g.,only) visually indicates (e.g., highlights) a complication previewcorresponding to a complication for which the application is notavailable).

In FIG. 6F, in response to (e.g., or subsequent to) downloading,receiving, and/or detecting the first user interface template (e.g., asdescribed above with reference to FIGS. 6A-6E), computer system 600Bdisplays, via display generation component 602B, user interface 632B,where user interface 632B includes a preview 634B of the first userinterface template, and where computer system 600B already includes(e.g., has already installed) all respective applications correspondingto all complications that are included with the first user interfacetemplate.

As shown in FIG. 6F, user interface 632B includes a plurality ofcomplication previews 636B, 638B, 640B, 642B, 644B, 646B, 648B, and650B. Because all of the respective applications are already installedon, and thus are available on, computer system 600B, all of complicationpreviews 636B-650B correspond to respective complications for availableapplications, and computer system 600B does not visually indicate (e.g.,does not highlight) any of complication previews 636B-650B (e.g., ascomputer system 600B (e.g., only) visually indicates (e.g., highlights)a complication preview corresponding to a complication for which theapplication is not available).

In FIG. 6F, because all of the respective applications are alreadyinstalled on, and thus available on, the respective computer system(e.g., on computer system 600B), computer system 600A displays, in userinterface 632A, an affordance 652A for adding the user interfacecorresponding to the first user interface template to a user interfacelibrary for the respective computer system (e.g., a collection of userinterfaces (e.g., watch user interfaces; watch faces) that can be usedon computer system 600B). While displaying affordance 652A, computersystem 600A receives (e.g., detects) an input 609A on affordance 652A.In some embodiments, input 609A is a touch input on display generationcomponent 602A. In response to receiving input 609A, computer system600A displays, via display generation component 602A, a companionapplication (e.g., an application that can be used to edit or configurefeatures and settings of a paired computer system) for the respectivecomputer system (e.g., a companion application for computer system600B), as shown in FIG. 6G.

Similarly, in FIG. 6F, because all of the respective applications arealready installed on, and thus available on, computer system 600B,computer system 600B displays, in user interface 632B, an affordance652B for adding the user interface corresponding to the first userinterface template to the user interface library for computer system600B. While displaying affordance 652B, computer system 600B receives(e.g., detects) an input 609B on affordance 652B. In some embodiments,input 609B is a touch input on display generation component 602B. Inresponse to receiving input 609B, computer system 600B displays, viadisplay generation component 602B, a watch user interface correspondingto the first user interface template configured in FIG. 6F, as shown inFIG. 6G.

In FIG. 6G, user interface 654 of the companion application includes aplurality of watch user interface previews that can be used as a watchuser interface on the respective computer system (e.g., on computersystem 600B), including a watch user interface preview 656A (includingcomplication previews 636A-650A) corresponding to the watch userinterface configured in FIG. 6F and shown as watch user interface 656Bon computer system 600B in FIG. 6G. As shown by computer system 600B,watch user interface 656B includes complications 658, 660, 662, 664,666, 668, 670, and 672, corresponding to complication previews 636B,638B, 640B, 642B, 644B, 646B, 648B, and 650B from FIG. 6F, respectively,where complications 658, 660, 662, 664, 666, 668, 670, and 672 can beused to perform operations on computer system 600B corresponding to therespective applications.

In some embodiments, for certain types of complications of a watch userinterface that is created from a received user interface template (e.g.,watch user interface 656B created from the first user interfacetemplate), how one or more settings of a respective compilation of thewatch user interface are set depends (e.g., at least partially) on thetype of the respective complications and/or a logic-based (e.g., asmart) algorithm.

For example, watch user interface 656B includes calendar complication660 corresponding to a calendar application of computer system 600B. Insome embodiments (e.g., upon completing the configuration/setup of watchuser interface 656B in FIG. 6F), settings of calendar complication 660are automatically (e.g., without user input) set to settings of thecalendar application that is installed on computer system 600B andcalendar complication 660 retrieves information (e.g., scheduleinformation) from a user account that is associated with the calendarapplication that is installed on computer system 600B, as opposed tomaintaining the calendar complication settings and/or information thathad originally been associated with the first user interface template(e.g., based on a respective computer system of the sender/creator ofthe first user interface template) when the first user interfacetemplate was initially downloaded, received, and/or detected on computersystem 600.

For another example, watch user interface 656B includes weathercomplication 668 corresponding to a weather application of computersystem 600B. In some embodiments (e.g., upon completing theconfiguration/setup of watch user interface 656B in FIG. 6F), settingsof weather complication 668 are automatically (e.g., without user input)set to the settings of the weather application that is installed oncomputer system 600B, as opposed to maintaining the weather complicationsettings and/or information that had originally been associated with thefirst user interface template (e.g., based on a respective computersystem of the sender/creator of the first user interface template) whenthe first user interface template was initially downloaded, received,and/or detected on computer system 600.

For another example, watch user interface 656B includes world clockcomplication 672 corresponding to a world clock application of computersystem 600B. In some embodiments (e.g., upon completing theconfiguration/setup of watch user interface 656B in FIG. 6F), settingsof world clock complication 672 are automatically (e.g., without userinput) transferred over from the world clock complication settings thathad originally been associated with the first user interface template(e.g., based on a respective computer system of the sender/creator ofthe first user interface template) when the first user interfacetemplate was initially downloaded, received, and/or detected on computersystem 600B. For example, if the world clock complication had been,prior to being configured/setup for use on computer system 600B, set toa current location of its respective computer system, the location ofthe world clock complication 672 is automatically (e.g., without userinput) set to the current location of computer system 600B uponcompletion of the configuration/setup of watch user interface 656B foruse on computer system 600B. For another example, if the world clockcompilation had been, prior to being configured/setup for use oncomputer system 600B, set to a predetermined location (e.g., a setlocation; a selected location; a particular location), the locationsetting of the world clock complication 672 is automatically (e.g.,without user input) maintained to be the same predetermined locationupon completion of the configuration/setup of watch user interface 656Bfor use on computer system 600B (e.g., instead of being modified to bethe current location of computer system 600B).

FIGS. 6H-6K illustrates a method for configuring the first userinterface template for use on the respective computer system (e.g.,computer system 600B), where the first user interface templatecorresponds to a photo watch user interface (e.g., a photo watch face).

In some embodiments, a respective photo watch user interface includes anindication of a current time and is associated with a plurality ofselected photos that are displayed (e.g., one-by-one) as a background ofthe respective photo watch user interface. In some embodiments, theplurality of selected photos (e.g., up to a predetermined maximum numberof photos, such as 6 photos, 12 photos, or 24 photos) are selected to beincluded in the respective photo watch user interface. In someembodiments, the currently-displayed photo of the respective photo watchuser interface changes automatically (e.g., based on time; randomly). Insome embodiments, the currently-displayed photo of the respective photowatch user interface changes based on predetermined criteria (e.g., inresponse to detecting a predefined movement of the respective computersystem, such as, e.g., a wrist raise). In some embodiments, a userinterface template corresponding to the respective photo watch userinterface, when downloaded, received, and/or detected by computer system600A or computer system 600B, includes the plurality of selected photosthat are included with (e.g., shared with, and thus downloaded,received, and/or detected by computer system 600A or computer system600B together with) the respective user interface template. In someembodiments, the plurality of photos corresponds to photos that weredesignated for the respective photo watch user interface on a sourcecomputer system/source device of the respective user interface templatecorresponding to the respective photo watch user interface (e.g.,selected by a user that created the respective user interface templateon the source computer system/source device), and are shared togetherwith the respective user interface template from the source computersystem/source device. In some embodiments, a photo watch user interfaceincludes complications, and the processes described in FIGS. 6A-6G and6L-6AB with respect to watch user interfaces also apply to photo watchuser interfaces.

In FIG. 6H, computer system 600A displays, via display generationcomponent 602A, user interface 624A of the messaging application, whereuser interface 624A of the messaging application is displaying messageconversation 626A with a message participant (e.g., “Jane Appleseed”).Message conversation 626A includes a received electronic communicationthat includes (e.g., as an attachment) the first user interface template(e.g., shown as preview 6106A in message conversation 626A) interface,the plurality of selected photos associated with the first userinterface template, including photo 6108A, and a message 630A associatedwith the received electronic communication. While displaying preview6106A corresponding to the photo watch user interface, computer system600A receives (e.g., detects) an input 6103A directed to preview 6106A.In some embodiments, input 6103A is a touch input on display generationcomponent 602A.

Similarly, in FIG. 6H, computer system 600B displays, via displaygeneration component 602B, user interface 624B of the messagingapplication, where user interface 624B of the messaging application isdisplaying message conversation 626B with the message participant (e.g.,“Jane Appleseed”). Message conversation 626A includes a receivedelectronic communication that includes (e.g., as an attachment) thefirst user interface template (e.g., shown as preview 6106B in messageconversation 626B), the plurality of selected photos associated with thefirst user interface template, including photo 6108A, and a message 630Bassociated with the received electronic communication. While displayingpreview 6106B corresponding to the photo watch user interface, computersystem 600B receives (e.g., detects) an input 6103B directed to preview6106B. In some embodiments, input 6103B is a touch input on displaygeneration component 602B.

In response to (e.g., or subsequent to) receiving input 6103A, computerdevice 600A displays, via displays, via display generation component602A, user interface 632A for creating a watch user interface based onthe first user interface template, as shown in FIG. 6I. Similarly, inresponse to (e.g., or subsequent to) receiving input 6103B, computerdevice 600B displays, via displays, via display generation component602B, user interface 632B for creating a watch user interface based onthe first user interface template, as shown in FIG. 6I.

In FIG. 6I, computer device 600A displays, concurrently with preview6106A (showing photo 6108A) of the photo watch user interface in userinterface 632A, an affordance 652A for initiating a process for creatinga photo watch user interface for the respective computer system (e.g.,for computer system 600B) based on the photo watch user interfacecorresponding to preview 6106A. While displaying user interface 632Awith preview 6106A and affordance 652A, computer system 600A receives(e.g., detects) an input 6105A on affordance 652A. In some embodiments,input 6105A is a touch input on display generation component 602A.

Similarly, in FIG. 6I, computer device 600B displays, concurrently withpreview 6106B (showing photo 6108A) of the photo watch user interface inuser interface 632B, an affordance 652B for initiating a process forcreating a photo watch user interface for the respective computer system(e.g., for computer system 600B) based on the photo watch user interfacecorresponding to preview 6106B. While displaying user interface 632Bwith preview 6106B and affordance 652B, computer system 600B receives(e.g., detects) an input 6105B on affordance 652B. In some embodiments,input 6105B is a touch input on display generation component 602B.

In response to receiving input 6105A, computer system 600A displays, viadisplay generation component 602A, a user interface 6110A (e.g., aphoto-picker user interface) that includes the plurality of photosassociated with (and received with) the photo watch user interface,including photo 6108A, as shown in FIG. 6J. Similarly, in response toreceiving input 6105B, computer system 600B displays, via displaygeneration component 602B, a user interface 6110B (e.g., a photo-pickeruser interface) that includes the plurality of photos associated with(and received with) the photo watch user interface, including photo6108A, as shown in FIG. 6J.

In FIG. 6J, user interface 6110A includes the plurality of associatedphotos (e.g., where a user can navigate (e.g., scroll) through thephotos), including photo 6108A and 6114A, where all of the plurality ofphotos (e.g., 24 of 24 photos) are currently selected to be includedwith the photo watch user interface corresponding to preview 6106A. Insome embodiments, all associated photos are initially (e.g., when userinterface 6110A is launched) selected to be used in the photo watch userinterface, and one or more of the plurality of associated photos can bede-selected (by the user) via user interface 6110A such that theremaining selected photos will be displayed as the background in thephoto watch user interface if the photo watch user interface is used asthe current watch user interface on the respective computer system(e.g., on computer system 600B). In some embodiments, one or more of theplurality of associated photos that are selected (e.g., remainsselected) are stored on computer system 600A and/or on the respectivecomputer system (e.g., on computer system 600B). In some embodiments,one or more of the plurality of associated photos that are not selected(e.g., were de-selected by the user) are not stored on computer system600A and/or the respective computer system (e.g., on computer system600B) (e.g., and are instead removed/deleted).

While displaying the plurality of photos in user interface 6110A,computer system 600A concurrently displays an affordance 6112A forcompleting the configuration/setup of the photo watch user interfacewith the currently-selected photos. While displaying user interface6110A with all of the plurality of associated photos selected (e.g.,because none of the photos were de-selected by the user), computersystem 600A receives (e.g., detects) an input 6107A directed toaffordance 6112A. In some embodiments, input 6107A is a touch input ondisplay generation component 602A.

Similarly, in FIG. 6J, corresponding user interface 6110B includes theplurality of associated photos, including photo 6108A and 6114A, whereall of the plurality of photos (e.g., 24 of 24 photos) are currentlyselected to be included with the photo watch user interfacecorresponding to preview 6106A. In some embodiments, one or more of theplurality of associated photos that are selected (e.g., remainsselected) are stored on computer system 600B. In some embodiments, oneor more of the plurality of associated photos that are not selected(e.g., were de-selected by the user) are not stored on computer system600B (e.g., and are instead removed/deleted). While displaying theplurality of photos in user interface 6110B, computer system 600Bconcurrently displays an affordance 6112B for completing theconfiguration/setup of the photo watch user interface with thecurrently-selected photos. While displaying user interface 6110B withall of the plurality of associated photos selected (e.g., because noneof the photos were de-selected by the user), computer system 600Breceives (e.g., detects) an input 6107B directed to affordance 6112B. Insome embodiments, input 6107B is a touch input on display generationcomponent 602B.

In response to receiving input 6107A on affordance 6112A, computersystem 600A displays, via display generation component 602A, userinterface 654 of the companion application, as shown in FIG. 6K.Similarly, in response to receiving input 6107B on affordance 6112B,computer system displays, via display generation component 602B, a photowatch user interface 6116B corresponding to the photo watch userinterface configured in FIG. 6J set as the current watch user interface,as shown in FIG. 6K.

In FIG. 6K, user interface 654 of the companion application includes, asone of the plurality of watch user interface previews that can be usedas a watch user interface on the respective computer system (e.g., oncomputer system 600B), photo watch user interface preview 6106Acorresponding to the photo watch user interface configured in FIG. 6J,and corresponding to photo watch user interface 6116B displayed incomputer system 600B as the current watch user interface.

FIG. 6L illustrates computer system 600A displaying, via displaygeneration component 602A, user interface 632A where two of therespective eight applications—the first application corresponding tocomplication preview 636A and the fifth application corresponding to thecomplication preview 644A—are not available on (e.g., not downloaded on;not installed on) the respective computer system (e.g., computer system600B). In some embodiments, the unavailable applications correspond tothird-party applications (e.g., as opposed to first-party applicationsdeveloped and published by the same entity controlling the operatingsystem of computer system 600B), where the third-party applications areavailable for download onto the respective computer system (e.g., ontocomputer system 600B) via a source (e.g., a website or an applicationstore) that is accessible on computer system 600A and/or the respectivecomputer system (e.g., computer system 600B).

In FIG. 6L, because the first application and the fifth application arenot available on the respective computer system (e.g., on computersystem 600B), computer system 600A visually indicates (e.g., dims;highlights) complication previews 636A and 644A, thereby indicating thatthe first and fifth applications are currently not available on therespective computer system (e.g., computer system 600B). In someembodiments, visually indicating complication previews 636A and 644Aincludes visually highlighting complication previews 636A and 644A whilenot visually highlighting the other complication previews. In someembodiments, visually indicating complication previews 636A and 644Aincludes dimming (e.g., darkening; shading) complication previews 636Aand 644A while not dimming the other complication previews. visuallyindicating complication previews 636A and 644A includes not dimmingcomplication previews 636A and 644A while dimming the other complicationpreviews.

FIG. 6L similarly illustrates computer system 600B displaying, viadisplay generation component 602B, user interface 632B where the firstapplication corresponding to complication preview 636B and the fifthapplication corresponding to the complication preview 644B are notavailable on computer system 600B. In FIG. 6L, because the firstapplication and the fifth application are not available on computersystem 600B, computer system 600B visually indicates (e.g., dims;highlights) complication previews 636B and 644B, thereby indicating thatthe first and fifth applications are currently not available on computersystem 600B.

In FIG. 6L, computer system 600A displays, in user interface 632A, anaffordance 674A for continuing with the configuration/setup process forenabling the user interface corresponding to preview 634A to be used onthe respective computer system (e.g., on computer system 600B). Whiledisplaying affordance 674A, computer system 600A receives (e.g.,detects) an input 611A on affordance 674A. In some embodiments, input611A is a touch input on display generation component 602A.

Similarly, in FIG. 6L, computer system 600B displays, in user interface632B, an affordance 674B for continuing with the configuration/setupprocess for enabling the user interface corresponding to preview 634B tobe used on computer system 600B. While displaying affordance 674B,computer system 600B receives (e.g., detects) an input 611B onaffordance 674B. In some embodiments, input 611B is a touch input ondisplay generation component 602B.

In some embodiments, if the computer system (computer system 600A or600B) does not receive an input on the affordance (affordance 674A or674B) for continuing with the configuration/setup process for apredetermined time period (e.g., 10 seconds; 15 seconds; 30 seconds),the computer system automatically (e.g., without any further user input)completes the configuration/setup process, where a new watch userinterface generated from the first user interface template becomesavailable for use on the respective computer system (e.g., on computersystem 600B) without including complications that correspond to theunavailable applications.

In response to receiving input 611A on affordance 674A, computer system600A displays, via display generation component 602A, user interface632A as shown in FIG. 6M. Similarly, in response to receiving input 611Bon affordance 674B, computer system 600B displays, via displaygeneration component 620B, user interface 632B as shown in FIG. 6M.

In FIG. 6M, computer system 600A visually highlights complicationpreview 636A corresponding to the first application without visuallyhighlighting the other complication previews (including not visuallyhighlighting complication preview 644A corresponding to the unavailablefifth application), thereby indicating that the current step in theconfiguration/setup process relates to first application correspondingto complication preview 636A. In some embodiments, computer system 600Aconcurrently displays, in user interface 632A, an indication 676A (e.g.,text information) that the current step in the configuration/setupprocess relates to one of the complications of the first user interfacetemplate for which the respective application is not available on therespective computer system (e.g., on computer system 600B), and of thecurrent stage within the configuration/setup process (e.g., “1 of 2”).

While visually highlighting complication preview 636A, computer system600A displays, in user interface 632A, an affordance 678A fordownloading (e.g., via an application store) the first applicationcorresponding to complication preview 636A, and an affordance 680A forcontinuing the configuration/setup process without downloading the firstapplication. While displaying affordances 678A and 680A, computer system600A receives (e.g., detects) an input 613A on affordance 680A.

Similarly, in FIG. 6M, computer system 600B visually highlightscomplication preview 636B corresponding to the first application withoutvisually highlighting the other complication previews (including notvisually highlighting complication preview 644B corresponding to theunavailable fifth application). In some embodiments, computer system600B concurrently displays, in user interface 632B, an indication 676B(e.g., text information) that the current step in theconfiguration/setup process relates to one of the complications of thefirst user interface template for which the respective application isnot available on computer system 600B, and of the current stage withinthe configuration/setup process (e.g., “1 of 2”).

While visually highlighting complication preview 636B, computer system600B displays, in user interface 632B, an affordance 678B fordownloading (e.g., via an application store) the first applicationcorresponding to complication preview 636B, and an affordance 680B forcontinuing the configuration/setup process without downloading the firstapplication. While displaying affordances 678B and 680B, computer system600B receives (e.g., detects) an input 613B on affordance 680B.

In response to receiving input 613A, computer system 600A displays, viadisplay generation component 602A, user interface 632A as in FIG. 6N.Similarly, in response to receiving input 613B, computer system 600Bdisplays, via display generation component 602B, user interface 632B asin FIG. 6N.

In FIG. 6N, because the first application was not downloaded, preview634A does not (e.g., no longer) include complication preview 636Acorresponding to the first application that was not downloaded.

In FIG. 6N, computer system 600A visually highlights complicationpreview 644A corresponding to the fifth application without visuallyhighlighting the other complication previews in preview 634A, therebyindicating that the current step in the configuration/setup processrelates to the fifth application. In some embodiments, computer system600A updates display of, in user interface 632A, indication 676A (e.g.,text information) of the current step in the configuration/setup processto indicate the current stage within the configuration/setup process(e.g., “2 of 2”).

While visually highlighting complication preview 644A, computer system600A displays, in user interface 632A, an affordance 682A fordownloading (e.g., via an application store) the fifth application, andan affordance 684A for continuing the configuration/setup processwithout downloading the fifth application. While displaying affordances682A and 684A, computer system 600A receives (e.g., detects) an input615A on affordance 682A.

Similarly, in FIG. 6N, because the first application was not downloaded,preview 634B does not (e.g., no longer) include complication preview636B corresponding to the first application that was not downloaded.

In FIG. 6N, computer system 600B visually highlights complicationpreview 644B corresponding to the fifth application without visuallyhighlighting the other complication previews in preview 634B, therebyindicating that the current step in the configuration/setup processrelates to the fifth application. In some embodiments, computer system600B updates display of, in user interface 632B, indication 676B (e.g.,text information) of the current step in the configuration/setup processto indicate the current stage within the configuration/setup process(e.g., “2 of 2”).

While visually highlighting complication preview 644B, computer system600B displays, in user interface 632B, an affordance 682B fordownloading (e.g., via an application store) the fifth application, andan affordance 684B for continuing the configuration/setup processwithout downloading the fifth application. While displaying affordances682B and 684B, computer system 600B receives (e.g., detects) an input615B on affordance 682B.

In some embodiments, the fifth application corresponding to complicationpreview 644A/644B is installed on computer system 600A but is notinstalled on computer system 600B. In some embodiments, in accordancewith a determination that the fifth application is installed on computersystem 600A but is not installed on computer system 600B (e.g., andwhere computer system 600A (e.g., a smartphone) and computer system 600B(e.g., a smartwatch) are paired systems), computer system 600B does notvisually highlight complication preview 644B corresponding to the fifthapplication, forgoes displaying affordance 682B for downloading thefifth application and affordance 684B for continuing theconfiguration/setup process without downloading the fifth application,and instead automatically downloads (e.g., without user input) the fifthapplication (directly) from computer system 600A (e.g., via ashort-range connection (e.g., Bluetooth)).

In some embodiments, in accordance with a determination that the fifthapplication corresponding to complication preview 644A/644B is installedon computer system 600A but is not installed on computer system 600B(e.g., and where computer system 600A (e.g., a smartphone) and computersystem 600B (e.g., a smartwatch) are paired systems), computer system600B still visually highlights representation 644B corresponding to thefifth application and displays affordance 682B and affordance 684B as inFIG. 6N. In some embodiments, in accordance with (e.g., in response to)an input on affordance 682B, computer system 600B downloads the fifthapplication (directly) from computer system 600A (e.g., via ashort-range connection (e.g., Bluetooth)) (e.g., instead of downloadingthe fifth application via the Internet).

In some embodiments, while displaying user interface 632A as in FIG. 6N,if computer system 600A does not detect an input on affordance 682A fora predetermined time period (e.g., 10 seconds; 15 seconds; 30 seconds),computer system 600A automatically (e.g., without any user input)proceeds with the configuration/setup process without downloading thefifth application corresponding to complication preview 644A. Similarly,in some embodiments, while displaying user interface 632B as in FIG. 6N,if computer system 600B does not detect an input on affordance 682B forthe predetermined time period (e.g., 10 seconds; 15 seconds; 30seconds), computer system 600B automatically (e.g., without any userinput) proceeds with the configuration/setup process without downloadingthe fifth application corresponding to complication preview 644B oncomputer system 600B.

In response to receiving input 615A, computer system 600A displays, viadisplay generation component 602A, user interface 632A as in FIG. 6O.Similarly, in response to receiving input 615B, computer system 600Bdisplays, via display generation component 602B, user interface 632B asin FIG. 6O.

In FIG. 6O, computer system 600A displays, via display generationcomponent 602A, a user interface 686A of an application store, whereuser interface 686A corresponds to a page of the application storerelating to the fifth application, and where user interface 686Aincludes an affordance 688A for downloading the fifth application ontocomputer system 600A. In some embodiments, the application store is afirst-party application developed and controlled by the same entitycontrolling the operating system of computer system 600A, and from whichfirst-party and/or third-party applications can be downloaded ontocomputer system 600A. In some embodiments, applications that aredownloaded onto computer system 600A can also be installed on therespective computer system (e.g., on computer system 600B) (e.g.,directly from computer system 600A to computer system 600B via acompanion application on computer system 600A). While displaying userinterface 686A, computer system 600A receives (e.g., detects) an input617A on affordance 688A. In some embodiments, input 617A is a touchinput on display generation component 602A.

Similarly, in FIG. 6O, computer system 600B displays, via displaygeneration component 602B, a user interface 686A of the applicationstore, where user interface 686A corresponds to the page of theapplication store relating to the fifth application, and where userinterface 686B includes an affordance 688B for downloading the fifthapplication onto computer system 600B. While displaying user interface686B, computer system 600B receives (e.g., detects) an input 617B onaffordance 688B. In some embodiments, input 617B is a touch input ondisplay generation component 602B.

In response to receiving input 617A on affordance 688A, computer system600A initiates a process for downloading the fifth application ontocomputer system 600A, as in FIG. 6P. Similarly, in response to receivinginput 617B on affordance 688B, computer system 600B initiates a processfor downloading the fifth application onto computer system 600B, as inFIG. 6P.

In FIG. 6P, computer system 600A displays, overlaid on a portion of userinterface 686A, an authorization user interface 690 for authorizing thedownloading (and installing) of the fifth application onto computersystem 600A. In some embodiments, authorization user interface 690includes instructions 692A for how to authorize and/or initiate thedownloading (and installing) of the fifth application onto computersystem 600A. In some embodiments, while displaying authorization userinterface 690, computer system 600A receives, via an input device 694A,an input 619A (e.g., a double-press input on a mechanical input buttonof computer system 600A) in accordance with instructions 692A.

Similarly, in FIG. 6P, computer system 600B displays, overlaid on userinterface 686B, instructions 692B for how to authorize and/or initiatethe downloading (and installing) of the fifth application onto computersystem 600B. In some embodiments, while displaying instructions 692B,computer system 600B receives, via an input device 694B, an input 619B(e.g., a double-press input on a mechanical input button of computersystem 600B) in accordance with instructions 692B.

In response to receiving input 619A while displaying authorization userinterface 690, computer system 600A downloads and installs the fifthapplication on computer system 600A (e.g., and, after having downloaded(and installed) the fifth application onto computer system 600A, causesthe fifth application to be installed on the respective computer system(e.g., on computer system 600B)). Similarly, in response to receivinginput 619B while displaying instructions 692B, computer system 600Bdownloads and installs the fifth application on computer system 600B.

FIG. 6Q illustrates computer system 600A displaying, via displaygeneration component 602A, user interface 623A showing preview 634Aafter (e.g., in response to) downloading and installing the fifthapplication on the respective computer system (e.g., on computer system600B). In FIG. 6Q, preview 634A includes complication preview 644Acorresponding to the fifth application that is not visually highlighted,thereby indicating that the respective complication corresponding tocomplication preview 644A can be used on the watch user interfacecorresponding to preview 634A once the configuration/setup process hasbeen completed. As also shown in FIG. 6Q, preview 634A still includesdisplay of the other complication previews corresponding to respectivecomplications that can be used (e.g., because their respectiveapplications were already available on (e.g., installed on) therespective computer system (e.g., on computer system 600B)) on the watchuser interface corresponding to preview 634A once theconfiguration/setup process has been completed.

While displaying user interface 623A showing preview 634A as in FIG. 6Q,computer system 600A concurrently displays, in user interface 632A, anaffordance 696A for completing the configuration/setup process forenabling the user interface corresponding to the first user interfacetemplate for use on the respective computer system (e.g., on computersystem 600B) without the first watch complication, and an affordance698A for continuing the configuration/setup process to initiate thedownloading of one or more applications that had not been downloaded(e.g., the first application).

While displaying affordances 696A and 698A, computer system 600Areceives (e.g., detects) an input 621A on affordance 696A for completingthe configuration/setup process. In some embodiments, input 621A is atouch input on display generation component 602A. In response todetecting input 621A on affordance 696A, computer system 600A completesthe configuration/setup process. In some embodiments, in response to(e.g., or subsequent to) completing the configuration/setup process,computer system 600A displays, via display generation component 602A,user interface 654 of the companion application (first described abovewith reference to FIG. 6K), where user interface 654 includes a watchuser interface preview corresponding to the new watch user interfacecreated in FIG. 6Q.

Similarly, FIG. 6Q also illustrates computer system 600B displaying, viadisplay generation component 602B, user interface 623B showing preview634B after (e.g., in response to) downloading and installing the fifthapplication on computer system 600B. In FIG. 6Q, preview 634B includescomplication preview 644B corresponding to the fifth application that isnot visually highlighted, thereby indicating that the respectivecomplication corresponding to complication preview 644B can be used onthe watch user interface corresponding to preview 634B once theconfiguration/setup process has been completed. As also shown in FIG.6Q, preview 634B still includes display of the other complicationpreviews corresponding to respective complications that can be used(e.g., because their respective applications were already available on(e.g., installed on) computer system 600B) on the watch user interfacecorresponding to preview 634A once the configuration/setup process hasbeen completed.

While displaying user interface 623B showing preview 634B as in FIG. 6Q,computer system 600B concurrently displays, in user interface 632B, anaffordance 696B for completing the configuration/setup process forenabling the user interface corresponding to the first user interfacetemplate for use on computer system 600B without the first watchcomplication, and an affordance 698B for continuing theconfiguration/setup process to initiate the downloading of one or moreapplications that had not been downloaded (e.g., the first application).

While displaying affordances 696B and 698B, computer system 600Breceives (e.g., detects) an input 621A on affordance 696B for completingthe configuration/setup process. In some embodiments, input 621B is atouch input on display generation component 602B. In response todetecting input 621B on affordance 696B, computer system 600B completesthe configuration/setup process. In some embodiments, in response to(e.g., or subsequent to) completing the configuration/setup process,computer system 600B displays, via display generation component 602B,the new watch user interface created in FIG. 6Q as the current watchuser interface.

As described above with reference to FIG. 6B, in some embodiments, thefirst user interface template can be downloaded and/or received via theapplication store on the computer (computer system 600A or computersystem 600B). In some embodiments, in response to receiving (e.g.,detecting) a request to download/receive the first user interfacetemplate via the application store, in accordance with a determinationthat one or more respective applications corresponding to the first userinterface template is not installed on (e.g., is not available on) therespective computer system (e.g., on computer system 600B), the computersystem displays an indication (e.g., a notification; a prompt; arequest) indicating that that the one or more respective applications(e.g., the first application and the fifth application) are notinstalled, and requesting authorization to download the one or morerespective applications (e.g., the first application and the fifthapplication) that are not installed (e.g., via the application store;concurrently as part of the process of downloading the first userinterface template from the application store). In some embodiments, inresponse to receiving (e.g., detecting) a request to download/receivethe first user interface template via the application store, thecomputer system downloads the first user interface template via theapplication store. In some embodiments, after (e.g., immediately after,in response to) downloading (e.g., and installing) the first userinterface template and in accordance with a determination that one ormore respective applications corresponding to the first user interfacetemplate is not installed on (e.g., is not available on) the respectivecomputer system (e.g., on computer system 600B), the computer systemdisplays an indication (e.g., a notification; a prompt; a request)indicating that that the one or more respective applications (e.g., thefirst application and the fifth application) are not installed, andrequests authorization to download the one or more respectiveapplications that are not installed.

FIG. 6R illustrates computer system 600A displaying, via displaygeneration component 602A, user interface 632A, where user interface632A includes preview 634A corresponding to the first user interfacetemplate if the fifth application corresponding to complication preview644A had not been downloaded onto computer system 600A (e.g., becauseaffordance 684A, instead of affordance 682A, had been activated in FIG.6N).

In FIG. 6R, because the fifth application had not been downloaded,preview 634A does not include complication preview 636A corresponding tothe first application and does not include complication preview 644Acorresponding to the fifth application. As in FIG. 6Q, because adecision has been made (as to whether to download each of the respectiveapplications that were not available on the respective computer system(e.g., on computer system 600B)) for each of the respective applicationsthat were not available on the respective computer system (e.g., oncomputer system 600B), computer system 600A displays, in user interface632A, affordance 696A for completing the configuration/setup process forenabling the user interface corresponding to the first user interfacetemplate for use on the respective computer system (e.g., on computersystem 600B) without the complications corresponding to the first andfifth applications, and affordance 698A for returning to theconfiguration/setup process to initiate the downloading of one or moreapplications that had not been downloaded.

Similarly, in FIG. 6R, because the fifth application had not beendownloaded, preview 634B does not include complication preview 636Bcorresponding to the first application and does not include complicationpreview 644B corresponding to the fifth application. As in FIG. 6Q,because a decision has been made (as to whether to download each of therespective applications that were not available on computer system 600B)for each of the respective applications that were not available oncomputer system 600B, computer system 600B displays, in user interface632B, affordance 696B for completing the configuration/setup process forenabling the user interface corresponding to the first user interfacetemplate for use on computer system 600B without the complicationscorresponding to the first and fifth applications, and affordance 698Bfor returning to the configuration/setup process to initiate thedownloading of one or more applications that had not been downloaded.

In response to receiving input 621A on affordance 696A in FIG. 6Q,computer system 600A displays, via display generation component 602A,user interface 654 that includes watch user interface preview 699A as inFIG. 6S. Similarly, in response to receiving input 621B on affordance696B in FIG. 6Q, computer system 600B displays, via display generationcomponent 602B, a watch user interface 699B (corresponding to watch userinterface preview 699A) as in FIG. 6S.

In FIG. 6S, user interface 654 includes watch user interface preview699A (including complication previews 638A-650A) corresponding to theuser interface for which configuration/setup was completed in FIG. 6Q,thereby indicating that the watch user interface corresponding topreview 699A is available for use on the respective computer system(e.g., on computer system 600B). Computer system 600B shows thecorresponding watch user interface (watch user interface 699B) beingused on computer system 600B as the current watch user interface, wherewatch user interface 699B includes complications 697-685 correspondingto complication previews 638A-650A, respectively.

FIG. 6T illustrates a computer system 600C (e.g., a smartphone) and acomputer system 600D (e.g., a smartwatch). In some embodiments, computersystem 600C is paired with computer system 600D. In some embodiments,computer system 600C can be used to control and/or manage configurationsand settings on computer system 600D (e.g., via a companion applicationfor computer system 600D that is accessible on computer system 600C).

In FIG. 6T, computer system 600C displays, via a display generationcomponent 602C, a user interface 683 (e.g., similar to user interface654 first described above with reference to FIG. 6F) for setting and/orediting user interface settings for a respective computer system (e.g.,for computer system 600D), including selecting a watch user interfacefor use on the respective computer system (e.g., on computer system600D). In some embodiments, user interface 683 includes a watch userinterface preview 681 corresponding to watch user interface 679displayed by computer system 600B in FIG. 6T.

While displaying user interface 683, computer system 600C receives(e.g., detects) an input 623A on watch user interface preview 681corresponding to watch user interface 679. In some embodiments, input623A is a touch input on display generation component 602A. Whiledisplaying watch user interface 679, computer system 600D receives(e.g., detects) an input 623B on watch user interface 679. In someembodiments, input 623B is a touch input on display generation component602B. In some embodiments, input 623B is a press input (e.g., apress-and-hold input) on display generation component 602B.

In response to receiving input 623A, computer system 600C displays, viadisplay generation component 602C, a user interface 677 for managingsettings associated with watch user interface 679, as shown in FIG. 6U.In response to receiving input 623B, computer system 600D displays, viadisplay generation component 602D, a user interface 655 for editing oneor more features (e.g., complication types) of watch user interface 679.

In FIG. 6U, user interface 677 displayed in computer system 600Aincludes a watch user interface preview 675 of watch user interface 679.In some embodiments, user interface 677 includes user interface elements673-659 for setting a complication type for a respective complicationincluded in watch user interface 679. In some embodiments, userinterface 677 includes an affordance 657A for initiating a sharing ofwatch user interface 679 (e.g., initiating a process forsending/transmitting watch user interface 679, as a user interfacetemplate, to a different computer system). While displaying userinterface 677, computer system 600C receives (e.g., detects) an input625A on affordance 657A. In some embodiments, input 625A is a touchinput on affordance 657A.

In FIG. 6U, user interface 655 displayed in computer system 600Bincludes a watch user interface preview 653 of watch user interface 679an affordance 657B (corresponding to affordance 657A) for initiating asharing of watch user interface 679 (e.g., initiating a process forsending/transmitting watch user interface 679, as a user interfacetemplate, to a different computer system). While displaying userinterface 655, computer system 600D receives (e.g., detects) an input625B on affordance 657B. In some embodiments, input 625B is a touchinput on affordance 657B.

In response to receiving input 625A on affordance 657A, computer system600C displays, via display generation component 602C, a user interface651A for selecting a recipient (e.g., from a contactable users list) ofthe user interface template corresponding to watch user interface 679being shared and/or for selecting a type of communication channel totransmit the user interface template, as shown in FIG. 6V. Similarly, inresponse to receiving input 625B on affordance 657B, computer system600D displays, via display generation component 602D, a user interface651B for selecting a recipient (e.g., from a contactable users list) ofthe user interface template corresponding to watch user interface 679being shared and/or for selecting a type of communication channel totransmit the user interface template, as shown in FIG. 6V.

In some embodiments, the user interface template (corresponding to watchuser interface 679) being shared can be transmitted from computer system600C to a computer system (e.g., an electronic device, such as asmartphone or a smartphone) of the recipient (e.g., an electronic devicelogged into an account associated with the recipient) via a messagingapplication (e.g., as an attachment of a message). In some embodiments,the user interface template being shared can be transmitted via a chatapplication. In some embodiments, the user interface template beingshared can be transmitted via an electronic mail application (e.g., asan attachment). In some embodiments, the user interface template beingshared can be transmitted via short-range communication (e.g., via NFC;via Bluetooth). In some embodiments, the user interface template beingshared can be transmitted by uploading the user interface template tothe Internet, from which the template is available for download by therecipient (e.g., by selecting a hyperlink corresponding to the uploadedtemplate).

In FIG. 6V, user interface 651A includes a plurality of contactableusers that can be selected as the recipient, including contactable users649A, 647A, and 645A. While displaying the plurality of contactableusers, computer system 600C receives (e.g., detects) an input 627Adirected to selecting contactable user 649A. In some embodiments, input627A is a touch input on display generation component 602A.

Similarly, in FIG. 6V, user interface 651B includes correspondingcontactable users available for selection as the recipient, including acontactable users 649B, 647B, and 645B. While displaying the pluralityof contactable users, computer system 600D receives (e.g., detects) aninput 627B directed to selecting contactable user 649B. In someembodiments, input 627B is a touch input on display generation component602B.

In response to receiving input 627A, computer device 600C displays, viadisplay generation component 602C, a user interface 643A of a messagingapplication, where user interface 643A includes a message conversation641A with contactable user 649A, as shown in FIG. 6W. Similarly, inresponse to receiving input 627B, computer system 600D displays, viadisplay generation component 602D, a user interface 643B of a messagingapplication, where user interface 643B includes a message conversation641B with contactable user 649B, as shown in FIG. 6W. As mentioned,sharing a watch user interface via a messaging application is one ofseveral different communication channels through which the watch userinterface can be shared with a different user.

In FIG. 6W, computer system 600C displays, in message conversation 641A,a preview 639A of the user interface template (corresponding to watchuser interface 679) being shared and an affordance 637A for initiatingthe transmittal of a message that includes the user interface templateto the recipient's computer system. While displaying messageconversation 641A, computer system 600C receives (e.g., detects) aninput 629A on affordance 637A. In some embodiments, input 629A is atouch input on display generation component 602A. In response toreceiving input 629A on affordance 637A, computer system 600C transmitsthe message that includes the user interface template corresponding towatch user interface 679 to the recipient's computer system (e.g.,similar to how computer system 600A received the first user interfacetemplate in FIG. 6E). Once received, the recipient can go through aprocess corresponding to the process described above with reference toFIGS. 6F-6S to configure/setup a new watch user interface based on theshared user interface template for use on the recipient's computersystem.

Similarly, in FIG. 6W, computer system 600D displays, in messageconversation 641B, a preview 639B of the user interface template(corresponding to watch user interface 679) being shared and anaffordance 637B for initiating the transmittal of a message thatincludes the user interface template to the recipient's computer system.While displaying message conversation 641B, computer system 600Dreceives (e.g., detects) an input 629B on affordance 637B. In someembodiments, input 629B is a touch input on display generation component602B. In response to receiving input 629B on affordance 637B, computersystem 600D transmits the message that includes the user interfacetemplate corresponding to watch user interface 679 to the recipient'scomputer system for use by the recipient.

FIG. 6X illustrates computer system 600B displaying, via displaygeneration component 602B, a first type of notification 635A (e.g., aprompt) concerning the configuration/setup process for a downloaded,received, and/or detected user interface template. In some embodiments,computer system 600B is not capable of directly downloading applications(e.g., from an application store or a website) onto computer system 600B(e.g., because computer system 600B does not have direct access to theInternet). In some embodiments, in accordance with a determination thatcomputer system 600B is not capable of directly downloading applicationsonto computer system 600B (e.g., and upon detecting a request toinitiate the process for configuring/setting up a new user interfacetemplate using computer system 600B), computer system 600B displaysnotification 635A indicating that that the process should be initiatedon a different computer system (e.g., a computer system that is pairedwith computer system 600B, such as computer system 600A (e.g., asmartphone)) and/or indicating that one or more applications associatedwith the user interface template that are not currently available oncomputer system 600B should first be downloaded onto the differentcomputer system (e.g., a computer system that is paired with computersystem 600B, such as computer system 600A).

FIG. 6Y illustrates computer system 600B displaying, via displaygeneration component 602B, a second type of notification 635B (e.g., aprompt) concerning the configuration/setup process for the downloaded,received, and/or detected user interface template. In some embodiments,computer system 600B is not capable of directly downloading applications(e.g., from a website or an application store) onto computer system 600B(e.g., because computer system 600B does not have direct access to theInternet). In some embodiments, in accordance with a determination thatcomputer system 600B is not capable of directly downloading applicationsfrom an application store onto computer system 600B (e.g., and upondetecting a request to initiate the process for configuring/setting up auser interface template using computer system 600B), computer system600B displays notification 635B indicating that one or more applicationsassociated with the user interface template that are not currentlyavailable on computer system 600B should first be downloaded via anapplication store accessed on the different computer system (e.g., acomputer system that is paired with computer system 600B, such ascomputer system 600A). In some embodiments, notification 635B alsoincludes an affordance 633 (e.g., a selectable user interface object; anactivatable user interface object) which, when activated (e.g., whenselected), (e.g., immediately) completes the configuration/setup processand adds the user interface corresponding to the new user interfacetemplate to a user interface library of computer system 600B.

FIG. 6Z illustrates computer system 600A displaying, via displaygeneration component 602A, a third type of notification 635C (e.g., anotification user interface) indicating that the type of user interfacecorresponding to the downloaded, received, and/or detected userinterface template can only be used on certain types (e.g., certainmodels) of computer systems, and that the type of user interfacecorresponding to the user interface template cannot be used on (e.g.,the new user interface template is not compatible with) the respectivecomputer system (e.g., computer system 600B).

FIG. 6AA illustrates computer system 600A displaying, via displaygeneration component 602A, a fourth type of notification 635D (e.g., anotification user interface) indicating that software (e.g., operatingsystem software; operating system version) on the respective computersystem (e.g., computer system 600B) for which the user interfacecorresponding to the downloaded, received, and/or detected userinterface template is to be used needs to be updated in order for theuser interface corresponding to the user interface template to be ableto be used on the respective computer system (e.g., on computer system600B). In some embodiments, notification 635D includes an affordance 631(e.g., a selectable user interface object; an activatable user interfaceobject) that, when activated, initiates a process for updating thesoftware (e.g., operating system software; operating system version) onthe respective computer system (e.g., on computer system 600B).

FIG. 6AB illustrates computer system 600A displaying, via displaygeneration component 602A, a fifth type of notification 635E (e.g., anotification user interface) indicating that (e.g., for a miscellaneousreason) the user interface (e.g., or the type of user interface)corresponding to the downloaded, received, and/or detected userinterface template cannot be used on the respective computer system(e.g., on computer system 600B).

FIGS. 7A-7F are a flow diagram illustrating a method for managing userinterface sharing using a computer system (e.g., an electronic device),in accordance with some embodiments. Method 700 is performed at acomputer system (e.g., an electronic device (e.g., 100, 300, 500, 600A,600B)) that is in communication with a display generation component(e.g., a display, a touch-sensitive display (e.g., 112)). Someoperations in method 700 are, optionally, combined, the orders of someoperations are, optionally, changed, and some operations are,optionally, omitted.

As described below, method 700 provides an intuitive way for managinguser interface sharing. The method reduces the cognitive burden on auser for managing user interface sharing, thereby creating a moreefficient human-machine interface. For battery-operated computer systems(e.g., computing devices; electronic devices), enabling a user to manageuser interface sharing faster and more efficiently conserves power andincreases the time between battery charges.

The computer system (e.g., 600A; 600B) receives (702) (e.g., from asecond computer system (e.g., a second electronic device; a second smartdevice, such as a second smartphone or a second smartwatch; an externalserver)), a representation (e.g., 634A; 634B) of a first user interfacetemplate (e.g., a template of a watch face or clock user interfacecreated by and/or shared by another user; a template of a watch face orclock user interface created on a different computer system orelectronic device and received from the different computer system orelectronic device) that specifies an arrangement of user interfaceelements (e.g., previews/images of watch complications; where the userinterface elements can include one or more of 636A, 638A, 640A, 642A,644A, 646A, 648A, 650A; 636B, 638B, 640B, 642B, 644B, 646B, 648B, and/or650B) including a first user interface element (e.g., a first watchcomplication) corresponding to a first application (e.g., theapplication that controls the corresponding first watch complication)and one or more other user interface elements (e.g., one or moreother/different watch complications corresponding to other/differentapplications; an indication of a time and/or date; or one or more otherwatch complications corresponding to a system feature) corresponding tosoftware that is different from the first application. Receiving arepresentation of a first user interface template that specifies anarrangement of user interface elements (e.g., as opposed to creating auser interface with the first user interface template on the computersystem) enables convenient creation of user interfaces and reduces thenumber of inputs needed to create a user interface. Reducing the numberof inputs needed to perform an operation enhances the operability of thecomputer system and makes the user-system interface more efficient(e.g., by helping the user to provide proper inputs and reducing usermistakes when operating/interacting with the computer system) which,additionally, reduces power usage and improves battery life of thecomputer system by enabling the user to use the computer system morequickly and efficiently.

In some embodiments, the representation (e.g., 634A; 634B) of the firstuser interface template is received via a message in a messageconversation (e.g., 626A; 626B; as an attachment file). In someembodiments, the representation of the first user interface template isreceived via NFC from a second computer system (e.g., 612; a secondelectronic device). In some embodiments, the representation of the firstuser interface template is received via a QR code scan (e.g., via 618).In some embodiments, the representation of the first user interfacetemplate is downloaded via a link (e.g., 610A; 610B) from a webpage(e.g., 606A; 606B). Providing various different methods toreceive/access to a user interface template enables convenient access tothe various different user interface templates. Providing additionalcontrol options/access to different operations for accessing the userinterface templates enhances the operability of the computer system andmakes the user-system interface more efficient (e.g., by helping theuser to provide proper inputs and reducing user mistakes whenoperating/interacting with the computer system) which, additionally,reduces power usage and improves battery life of the computer system byenabling the user to use the computer system more quickly andefficiently.

Subsequent to receiving the representation (e.g., 634A, 634B) of thefirst user interface template (e.g., and while displaying therepresentation of the first user interface template (or an indication orpreview of the first user interface template)), the computer system(e.g., 600A; 600B) receives (708) a request (e.g., 609A; 609B; 611A;611B) to use the first user interface template for a respective computersystem (e.g., 600B; the current computer system (e.g., the currentelectronic device), a different computer system (e.g., 600B; a differentelectronic device) that is paired with the current computer system(e.g., the current electronic device)) that includes a plurality ofinstalled applications.

In response to receiving (710) the request (e.g., 609A; 609B; 611A;611B) to use the first user interface template for the respectivecomputer system (e.g., 600B), the computer system (e.g., 600A; 600B)initiates (712) a process for (e.g., as shown in FIGS. 6F-6G, 6I-6J,and/or 6L-6R) creating a user interface for the respective computersystem using the first user interface template. Initiating the processfor creating a user interface for the respective computer system usingthe first user interface template provides quick and easy access to theprocess for creating the user interface. In some embodiments, theprocess for creating the user interface is initiated automaticallywithout user input. Reducing the number of inputs needed to perform anoperation enhances the operability of the computer system and makes theuser-system interface more efficient (e.g., by helping the user toprovide proper inputs and reducing user mistakes whenoperating/interacting with the computer system) which, additionally,reduces power usage and improves battery life of the computer system byenabling the user to use the computer system more quickly andefficiently.

The process for (e.g., as shown in FIGS. 6F-6G, 6I-6J, and/or 6L-6R)creating the user interface for the respective computer system (e.g.,600B) using the first user interface template includes (714), inaccordance with a determination that the first application is notavailable on (e.g., not installed on; not downloaded onto; not locallyaccessible on) the respective computer system, the computer system(e.g., 600A; 600B) displaying (716), via the display generationcomponent (e.g., 602A; 602B), an alert (e.g., user interface 632A ofFIG. 6M; user interface 632B of FIG. 6M; user interface 632A of FIG. 6N;user interface 632B of FIG. 6N; a notification; a prompt; a message; anaffordance) indicating that the first application needs to be installedon the respective computer system in order for the first user interfacetemplate to be used to create a user interface for the respectivecomputer system that includes the first user interface element from thefirst user interface template; and in accordance with a determinationthat the first application is available on (e.g., downloaded onto;installed on; locally accessible on) the respective computer system, thecomputer system forgoing displaying (718), via the display generationcomponent, the alert indicating that the first application needs to beinstalled on the respective computer system in order for the first userinterface template to be used to create a user interface for therespective computer system that includes the first user interfaceelement from the first user interface template. Displaying the alertindicating that the first application needs to be installed on therespective computer system in accordance with the determination that thefirst application is not available on the respective computer systemenables a user to quickly and easily recognize that further action mustbe taken to enable use of the user interface on the computer system.Providing improved visual feedback enhances the operability of thecomputer system and makes the user-system interface more efficient(e.g., by helping the user to provide proper inputs and reducing usermistakes when operating/interacting with the computer system) which,additionally, reduces power usage and improves battery life of thecomputer system by enabling the user to use the computer system morequickly and efficiently.

In some embodiments, the process for (e.g., as shown in FIGS. 6F-6G,6I-6J, and/or 6L-6R) creating the user interface for the respectivecomputer system (e.g., 600B) using the first user interface templateincludes (714), in accordance with the determination (724) that thefirst application is not available on the respective computer system,the computer system (e.g., 600A; 600B) displaying (724), via the displaygeneration component (e.g., 602A; 602B), an affordance (e.g., 678A;678B; 682A; 682B; an install affordance or an install prompt that can beselected to initiate the download and/or installing of the firstapplication on the computer system) that, when activated, initiates aprocess (e.g., displays an application store) for installing the firstapplication on the respective computer system (e.g., downloading thefirst application (e.g., from the application store; from an externalserver) onto the respective computer system and installing the firstapplication on the respective computer system). Displaying theaffordance that, when activated, initiates the process for installingthe first application on the respective computer system enables a userto easily control, during the configuration/setup process, whether ornot the first application should be installed on the respectivecomputer. Providing easily accessible control options enhances theoperability of the computer system and makes the user-system interfacemore efficient (e.g., by helping the user to provide proper inputs andreducing user mistakes when operating/interacting with the computersystem) which, additionally, reduces power usage and improves batterylife of the computer system by enabling the user to use the computersystem more quickly and efficiently.

In some embodiments, the affordance (e.g., 678A; 678B; 682A; 682B) isdisplayed after (e.g., in response to) receiving the request to use thefirst user interface template for the respective computer system (e.g.,600B). In some embodiments, the affordance is displayed concurrentlywith the alert (e.g., user interface 632A of FIG. 6M; user interface632B of FIG. 6M; user interface 632A of FIG. 6N; user interface 632B ofFIG. 6N) indicating that the first application needs to be installed onthe respective computer system in order for the first user interfacetemplate to be used to create a user interface for the respectivecomputer system that includes the first user interface element from thefirst user interface template. Displaying the affordance concurrentlywith the alert enables a user to quickly and easily recognize that theaffordance relates to the first user interface element that is indicated(e.g., highlighted) via the alert. Providing improved visual feedbackenhances the operability of the computer system and makes theuser-system interface more efficient (e.g., by helping the user toprovide proper inputs and reducing user mistakes whenoperating/interacting with the computer system) which, additionally,reduces power usage and improves battery life of the computer system byenabling the user to use the computer system more quickly andefficiently.

In some embodiments, the process for (e.g., as shown in FIGS. 6F-6G,6I-6J, and/or 6L-6R) creating the user interface for the respectivecomputer system (e.g., 600B) using the first user interface templateincludes, in accordance with a determination that the affordance (e.g.,678A; 678B; 682A; 682B) was not activated (e.g., the user affirmativelychooses to proceed without installing the first application (e.g., byselecting an affordance to continue without installing the firstapplication on the respective computer system or by selecting anaffordance to dismiss the affordance for installing the firstapplication on the respective computer system), the user does not selectthe affordance for a predetermined time period (e.g., 5 seconds; 10seconds) while the affordance was displayed), the computer system (e.g.,600A; 600B) continuing (728) the process for creating the user interfacefor the respective computer system using the first user interfacetemplate without installing (e.g., without downloading and installing)the first application on the respective computer system, where the firstuser interface template is configured to (e.g., set to; modified to) notinclude the first user interface element (e.g., the first watchcomplication) corresponding to the first application. Continuing (e.g.,automatically, without further user input) the process for creating theuser interface for the respective computer system if the user does notselect the affordance for a predetermined time period optimizes theconfiguration/setup process by enabling the process to proceed if a userinput is not detected for a prolonged period of time. Reducing thenumber of inputs needed to perform an operation enhances the operabilityof the computer system and makes the user-system interface moreefficient (e.g., by helping the user to provide proper inputs andreducing user mistakes when operating/interacting with the computersystem) which, additionally, reduces power usage and improves batterylife of the computer system by enabling the user to use the computersystem more quickly and efficiently.

In some embodiments, during the process for (e.g., as shown in FIGS.6F-6G, 6I-6J, and/or 6L-6R) creating the user interface for therespective computer system (e.g., 600B) using the first user interfacetemplate, while displaying the affordance (e.g., 678A; 678B; 682A;682B), the computer system (e.g., 600A; 600B) detects (e.g., via one ormore input devices of the computer system, such as a touch-sensitivesurface that is integrated with the display generation component (e.g.,602A; 602B)) an activation (e.g., 615A; 615B) of (e.g., user selectionof) the affordance, and in response to detecting the activation of theaffordance, initiates (730) the process for installing the firstapplication on the respective computer system. Enabling the initiationof the process for installing the first application via the affordanceprovided during the configuration/setup process enables a user toquickly and easily install the first application. Providing easilyaccessible control options enhances the operability of the computersystem and makes the user-system interface more efficient (e.g., byhelping the user to provide proper inputs and reducing user mistakeswhen operating/interacting with the computer system) which,additionally, reduces power usage and improves battery life of thecomputer system by enabling the user to use the computer system morequickly and efficiently.

In some embodiments, the process for (e.g., as shown in 6N-6O)installing the first application on the respective computer system(e.g., 600B) includes displaying (e.g., on the computer system (e.g.,600A; 600B) and/or on the respective computer system) an applicationstore (e.g., 6100A; 6100B; 686A; 686B) for downloading the firstapplication onto the respective computer system and/or downloading(e.g., automatically, without displaying the application store) thefirst application onto the respective computer system.

In some embodiments, the one or more other user interface elements(e.g., where the user interface elements can include one or more of636A, 638A, 640A, 642A, 644A, 646A, 648A, 650A; 636B, 638B, 640B, 642B,644B, 646B, 648B, and/or 650B) include (704) a second user interfaceelement (different from the first user interface element and arranged ata different location/position within the first user interface templatethan the first user interface element) (e.g., a second watchcomplication) corresponding to a second application different from thefirst application, where the process for creating the user interface forthe respective computer system (e.g., 600B) using the first userinterface template includes (e.g., after displaying the alert (732)indicating that the first application needs to be installed on therespective computer system or forgoing displaying the alert): inaccordance with a determination that the second application (e.g., thatcontrols the second user interface element) is not available on (e.g.,not installed on; not downloaded onto; not locally accessible on) therespective computer system, the computer system (e.g., 600A; 600B)displaying (720), via the display generation component (e.g., 602A;602B), a second alert (e.g., user interface 632A of FIG. 6H; userinterface 632B of FIG. 6H; user interface 732A of FIG. 6I; userinterface 632B of FIG. 6I; a notification; a prompt; a message)indicating that the second application needs to be installed on therespective computer system in order for the first user interfacetemplate to be used to create a user interface for the respectivecomputer system that includes the second user interface element from thefirst user interface template (e.g., the second alert is displayed afterthe computer system has displayed and is no longer displaying thealert); and in accordance with a determination that the secondapplication is available on (e.g., downloaded onto; installed on;locally accessible on) the respective computer system, the computersystem forgoing displaying (722), via the display generation component,the second alert indicating that the second application needs to beinstalled on the respective computer system in order for the first userinterface template to be used to create a user interface for therespective computer system that includes the second user interfaceelement from the first user interface template.

In some embodiments, the one or more other user interface elements(e.g., where the user interface elements can include one or more of636A, 638A, 640A, 642A, 644A, 646A, 648A, 650A; 636B, 638B, 640B, 642B,644B, 646B, 648B, and/or 650B) include a second user interface element(different from the first user interface element and arranged at adifferent location/position within the first user interface templatethan the first user interface element) (e.g., a second watchcomplication) corresponding to a second application different from thefirst application and a third user interface element (different from thefirst and second user interface elements and arranged at a differentlocation/position within the first user interface template than thefirst and second user interface elements) (e.g., a third watchcomplication) corresponding to a third application different from thefirst application and the second application, where the process forcreating the user interface for the respective computer system (e.g.,600B) using the first user interface template includes subsequent to(e.g., after) displaying the alert (e.g., user interface 632A of FIG.6H; user interface 632B of FIG. 6H; user interface 732A of FIG. 6I; userinterface 632B of FIG. 6I) (e.g., and while no longer displaying thealert), in accordance with a determination that the second application(e.g., that corresponds to the second user interface element) is notavailable on (e.g., not installed on; not downloaded onto; not locallyaccessible on) the respective computer system, the computer system(e.g., 600A; 600B) displaying (734), via the display generationcomponent (e.g., 602A; 602B), a second alert (736) (e.g., user interface632A of FIG. 6H; user interface 632B of FIG. 6H; user interface 732A ofFIG. 6I; user interface 632B of FIG. 6I; a notification; a prompt; amessage) indicating that the second application needs to be installed onthe respective computer system in order for the first user interfacetemplate to be used to create a user interface for the respectivecomputer system that includes the second user interface element from thefirst user interface template (e.g., the second alert is displayed afterthe computer system has displayed and is no longer displaying thealert), and subsequent to (e.g., after) displaying the second alert(e.g., and while no longer displaying the second alert), in accordancewith a determination that the third application (e.g., that controls thesecond user interface element) is not available on (e.g., not installedon; not downloaded onto; not locally accessible on) the respectivecomputer system, the computer system displaying (738), via the displaygeneration component, a third alert (e.g., user interface 632A of FIG.6H; user interface 632B of FIG. 6H; user interface 732A of FIG. 6I; userinterface 632B of FIG. 6I; a notification; a prompt; a message)indicating that the third application needs to be installed on therespective computer system in order for the first user interfacetemplate to be used to create a user interface for the respectivecomputer system that includes the third user interface element from thefirst user interface template (e.g., the third alert is displayed afterthe computer system has displayed and is no longer displaying the secondalert). Displaying the alert, second alert, and third alert sequentiallyduring the configuration/setup process enables the user to quickly andeasily recognize a missing application for each respective stage, andtherefore make an informed decision on whether or not to download themissing application. Providing improved control options enhances theoperability of the computer system and makes the user-system interfacemore efficient (e.g., by helping the user to provide proper inputs andreducing user mistakes when operating/interacting with the computersystem) which, additionally, reduces power usage and improves batterylife of the computer system by enabling the user to use the computersystem more quickly and efficiently.

In some embodiments, the representation (e.g., 634A; 634B) of the userinterface specifies (706) elements for the first application that is notavailable on (e.g., not installed on; not downloaded onto; not locallyaccessible on) the respective computer system and a second applicationthat is not available on (e.g., not installed on; not downloaded onto;not locally accessible on) the respective computer system (e.g., 600B).In some embodiments, the process for (e.g., as shown in FIGS. 6F-6G,6I-6J, and/or 6L-6R) creating the user interface for the respectivecomputer system using the first user interface template includes thecomputer system (e.g., 600A; 600B) displaying (740), via the displaygeneration component (e.g., 602A; 602B), a user interface for the firstuser interface element that includes a representation (e.g., 634A; 634B)of the first user interface template and one or more selectable userinterface objects associated with the first user interface element,where the representation of the first user interface template includesthe first user interface element corresponding to the first application(e.g., the representation of the first user interface templateoptionally includes a second user interface element (different from thefirst user interface element) corresponding to the second application).Displaying the user interface for the first user interface element thatincludes a representation of the first user interface template and oneor more selectable user interface objects associated with the first userinterface element during the configuration/setup process enables a userto quickly and easily recognize which, if any, applications may need tobe installed on the computer system, and also recognize updates to theuser interface as the user is making decisions for each of the userinterface objects for which user action is needed. Providing improvedvisual feedback enhances the operability of the computer system andmakes the user-system interface more efficient (e.g., by helping theuser to provide proper inputs and reducing user mistakes whenoperating/interacting with the computer system) which, additionally,reduces power usage and improves battery life of the computer system byenabling the user to use the computer system more quickly andefficiently.

In some embodiments, the representation (e.g., 634A; 634B) of the firstuser interface template is displayed in a setup user interface (e.g.,623A; 623B) for configuring different user interface templates to beused to create different user interfaces for use (e.g., for use as awatch face user interface) on the respective computer system (e.g.,600B).

In some embodiments, while displaying the representation (e.g., 634A;634B) of the first user interface template, and after receiving one ormore inputs corresponding to a decision as to whether to make the firstapplication available (e.g., install the first application), thecomputer system (e.g., 600A; 600B) receives (742) an input correspondingto a request to display a user interface for a second user interfaceelement that includes a representation of the first user interfacetemplate and one or more selectable user interface objects associatedwith the second user interface element.

In some embodiments, in response to receiving (744) the request todisplay a user interface for the second user interface element, inaccordance with a determination that (e.g., in accordance with receivinga request (e.g., detecting a user input)) the first application wasselected for installation (e.g., based on the one or more inputscorresponding to the decision as to whether to install the firstapplication) on the respective computer system (e.g., 600B), thecomputer system displaying (746) the user interface for the second userinterface element includes displaying a representation of the first userinterface element (e.g., as shown by watch user interface preview 634Ain FIG. 6Q and watch user interface preview 634B in FIG. 6Q); and inaccordance with a determination that (e.g., in accordance with receivinga request (e.g., detecting a user input); in accordance with apredetermined time period having passed) the first application was notselected for installation (e.g., based on the one or more inputscorresponding to the decision as to whether to install the firstapplication) on the respective computer system, the computer systemdisplaying (748) the user interface for the second user interfaceelement includes displaying the representation of the first userinterface template without displaying the first user interface element(e.g., as shown by watch user interface preview 634A and watch userinterface preview 634B in FIG. 6N). Displaying the representation of thefirst user interface element in accordance with a determination that thefirst application was selected for installation and displaying therepresentation of the first user interface template without displayingthe first user interface element in accordance with a determination thatthe first application was not selected for installation providesimproved visual feedback about user action taken during theconfiguration/setup process, which in turn enhances the operability ofthe computer system and makes the user-system interface more efficient(e.g., by helping the user to provide proper inputs and reducing usermistakes when operating/interacting with the computer system) which,additionally, reduces power usage and improves battery life of thecomputer system by enabling the user to use the computer system morequickly and efficiently.

In some embodiments, the representation (e.g., 634A; 634B) of the userinterface specifies elements for a third application that is notavailable on (e.g., not installed on; not downloaded onto; not locallyaccessible on) the respective computer system (e.g., the representationof the first user interface template includes a third user interfaceelement (different from the first user interface element and from thesecond user interface element) corresponding to the third application).In some embodiments, the process for creating the user interface for therespective computer system (e.g., 600B) using the first user interfacetemplate includes, while displaying the representation of the first userinterface template, and after receiving one or more inputs correspondingto a decision as to whether to make the second application available(e.g., install the first application), the computer system (e.g., 600A;600B) receiving (750) an input corresponding to a request to display auser interface for a third user interface element that includes arepresentation of the first user interface template and one or moreselectable user interface objects associated with the third userinterface element.

In some embodiments, in response to receiving (752) the request todisplay a user interface for the third user interface element, inaccordance with a determination that (e.g., in accordance with receivinga request (e.g., detecting a user input)) the second application wasselected for installation (e.g., based on the one or more inputscorresponding to the decision as to whether to install the firstapplication) on the respective computer system (e.g., to be downloadedand installed on the respective computer system; to be made available onthe respective computer system), the computer system displaying (754)the user interface for the third user interface element includesdisplaying a representation of the second user interface element (e.g.,no longer highlighting; dimming; blurring) (e.g., as shown by watch userinterface preview 634A in FIG. 6Q and watch user interface preview 634Bin FIG. 6Q); and in accordance with a determination that (e.g., inaccordance with receiving a request (e.g., detecting a user input); inaccordance with a predetermined time period having passed) the secondapplication was not selected for installation (e.g., based on the one ormore inputs corresponding to the decision as to whether to install thefirst application) on the respective computer system (e.g., to not bedownloaded and/or not be installed on the respective computer system),the computer system displaying (756) the user interface for the thirduser interface element includes displaying the representation of thefirst user interface template without displaying the second userinterface element (e.g., as shown by watch user interface preview 634Aand watch user interface preview 634B in FIG. 6N). Displaying therepresentation of the second user interface element in accordance with adetermination that the second application was selected for installationand displaying the representation of the first user interface templatewithout displaying the second user interface element in accordance witha determination that the second application was not selected forinstallation provides improved visual feedback about user action takenduring the configuration/setup process, which in turn enhances theoperability of the computer system and makes the user-system interfacemore efficient (e.g., by helping the user to provide proper inputs andreducing user mistakes when operating/interacting with the computersystem) which, additionally, reduces power usage and improves batterylife of the computer system by enabling the user to use the computersystem more quickly and efficiently.

In some embodiments, the process for (e.g., as shown in FIGS. 6F-6G,6I-6J, and/or 6L-6R) creating the user interface for the respectivecomputer system (e.g., 600B) using the first user interface templateincludes the computer system (e.g., 600A; 600B) displaying, via thedisplay generation component (e.g., 602A; 602B), the representation(e.g., 634A; 634B) of the first user interface template. In someembodiments, the representation of the first user interface template isdisplayed in a setup user interface (e.g., 632A; 632B) for configuringdifferent user interface templates to be used to create different userinterfaces for use (e.g., for use as a watch face user interface) on therespective computer system. In some embodiments, while displaying therepresentation of the first user interface template, in accordance withthe determination that the first application is not available on therespective computer system, the computer system displays, in therepresentation of the first user interface template, the first userinterface element with a first visual characteristic (e.g., highlighted,brightened, and/or otherwise visually indicated such that the first userinterface element is more visible/recognizable within the representationof the first user interface template) (e.g., as shown via complicationpreviews 636A and 636B in FIG. 6M and complication previews 644A and644B in FIG. 6N); and in accordance with the determination that thefirst application is available on the respective computer system, thecomputer system displays, in the representation of the first userinterface template, the first user interface element with a secondvisual characteristic (e.g., not highlighted; dimmed; blurred) differentfrom the first visual characteristic (e.g., as shown via complicationpreviews in FIG. 6L other than complication previews 636A, 644A and636B, 644B). Displaying the first user interface element with the firstvisual characteristic in accordance with the determination that thefirst application is not available on the respective computer systemenables a user to quickly and easily recognize that the firstapplication is not available (e.g., is not installed). Providingimproved visual feedback enhances the operability of the computer systemand makes the user-system interface more efficient (e.g., by helping theuser to provide proper inputs and reducing user mistakes whenoperating/interacting with the computer system) which, additionally,reduces power usage and improves battery life of the computer system byenabling the user to use the computer system more quickly andefficiently.

In some embodiments, if the representation (e.g., 634A; 634B) of thefirst user interface template includes a plurality of respective userinterface elements (e.g., 636A, 638A, 640A, 642A, 644A, 646A, 648A,650A; 636B, 638B, 640B, 642B, 644B, 646B, 648B, 650B) corresponding torespective applications that are unavailable on the respective computersystem (e.g., 600B), the computer system (e.g., 600A; 600B) displays, inthe representation of the first user interface template, the pluralityof respective user interface elements with the first visualcharacteristic (e.g., highlighted; brightened).

In some embodiments, receiving the representation (e.g., 634A; 634B) ofthe first user interface template comprises receiving (e.g., as anattachment; as a download link) the representation of the first userinterface template via a messaging application (e.g., 624A; 624B; a textmessaging application; a chat application; an electronic mailapplication). Receiving the representation of the first user interfacetemplate via the messaging application enables a user to convenientlyreceive the first user interface template from a different user.Providing convenient control options enhances the operability of thecomputer system and makes the user-system interface more efficient(e.g., by helping the user to provide proper inputs and reducing usermistakes when operating/interacting with the computer system) which,additionally, reduces power usage and improves battery life of thecomputer system by enabling the user to use the computer system morequickly and efficiently.

In some embodiments, receiving the representation (e.g., 634A; 634B) ofthe first user interface template includes the computer system (e.g.,600A; 600B) displaying, via the display generation component (e.g.,602A; 602B), a messaging user interface (e.g., 624A; 624B) showing amessaging conversation (e.g., 626A; 626B) with one or more otherparticipants of a messaging application (e.g., a text messagingapplication; a chat application; an email application). In someembodiments, the computer system (e.g., 600A; 600B) displays, in themessaging user interface, a first message (e.g., 628A; 628B)corresponding to the representation of the first user interfacetemplate, where the first message includes an image (e.g., a previewimage) showing the representation of the first user interface template.Displaying the first message where the message includes the imageshowing the representation of the first user interface template enablesa user to quickly and easily view the first user interface templatewithout needing to first download/store the first user interfacetemplate. Reducing the number of inputs needed to perform an operationenhances the operability of the computer system and makes theuser-system interface more efficient (e.g., by helping the user toprovide proper inputs and reducing user mistakes whenoperating/interacting with the computer system) which, additionally,reduces power usage and improves battery life of the computer system byenabling the user to use the computer system more quickly andefficiently.

In some embodiments, receiving the request (e.g., 609A; 609B; 6105A;6105B; 621A; 621B) to use the first user interface template for therespective computer system (e.g., 600B) includes detecting (e.g., viaone or more input devices of the computer system, such as atouch-sensitive surface that is in communication with the devicegeneration component) user selection of the image showing therepresentation (e.g., 628A; 628B) of the first user interface templatein the first message. In some embodiments, receiving the request to usethe first user interface template for the respective computer systemincludes detecting (e.g., via one or more input devices of the computersystem, such as a touch-sensitive surface that is in communication withthe device generation component) user selection of a link correspondingto the representation of the first user interface template.

In some embodiments, the process for (e.g., as shown in FIGS. 6F-6G,6I-6J, and/or 6L-6R) creating the user interface for the respectivecomputer system (e.g., 600B) using the first user interface templateincludes, in accordance with the determination that the firstapplication is not available on (e.g., not downloaded on; not installedon; not accessible on) the respective computer system (e.g., as shown in632B in FIG. 6M and 632B in FIG. 6N) (e.g., where the respectivecomputer system is the same system as the computer system) (e.g., inresponse to receiving the request to use the first user interfacetemplate for the respective computer system), the computer system (e.g.,600A; 600B) initiating (e.g., via a short-range communication radio thatis in communication with the computer system) a communication to asecond computer system (e.g., 600B; 600A; a second electronic device(e.g., a smartphone)) that is coupled to (e.g., paired with) thecomputer system (e.g., an electronic device), where the communicationincludes instructions to continue the process for creating the userinterface for the respective computer system using the first userinterface template on the second computer system (instead of on thecomputer system). Enabling the process for creating the user interfaceto continue on the second computer system enables a user to convenientlycomplete the process on a different computer system if, for example, theprocess cannot be completed on the current computer system (e.g.,because the current computer system does not have access to the Internetto download applications). Providing convenient control options enhancesthe operability of the computer system and makes the user-systeminterface more efficient (e.g., by helping the user to provide properinputs and reducing user mistakes when operating/interacting with thecomputer system) which, additionally, reduces power usage and improvesbattery life of the computer system by enabling the user to use thecomputer system more quickly and efficiently.

In some embodiments, the respective computer system (e.g., 600B) is thesame system as the computer system (e.g., the respective computer systemis the same device as the electronic device). In some embodiments, thecomputer system (e.g., 600B) is a wearable electronic device (e.g., asmartwatch). In some embodiments, the computer system does not have adirect connection with or direct access to the Internet. In someembodiments, the computer system is paired with (e.g., via a Bluetoothconnection) a second computer system (e.g., 600A; a smartphone).

In some embodiments, the process for (e.g., as shown in FIGS. 6F-6G,6I-6J, and/or 6L-6R) creating the user interface for the respectivecomputer system (e.g., 600B) using the first user interface templateincludes, in accordance with the determination that the firstapplication is not available on (e.g., not downloaded on; not installedon; not accessible on) the respective computer system (e.g., as shown in632B in FIG. 6M and 632B in FIG. 6N) (e.g., where the respectivecomputer system is the same system as the computer system) (e.g., inresponse to receiving the request to use the first user interfacetemplate for the respective computer system), the computer system (e.g.,600A; 600B) continuing the process for creating the user interface forthe respective computer system using the first user interface templatewithout installing (e.g., without downloading and installing) the firstapplication on the respective computer system (e.g., as shown via 632Aand 632B in FIG. 6M), where the first user interface template no longerincludes the first user interface element corresponding to the firstapplication (e.g., as shown in 632A and 632B in FIG. 6M). Enabling theprocess creating the user interface for the respective computer systemusing the first user interface template to continue without installingthe first application provides user control over which applicationsshould be installed and used for the user interface, and enablescompletion of the process even if not all unavailable (e.g., notinstalled) applications are installed. Providing improved controloptions enhances the operability of the computer system and makes theuser-system interface more efficient (e.g., by helping the user toprovide proper inputs and reducing user mistakes whenoperating/interacting with the computer system) which, additionally,reduces power usage and improves battery life of the computer system byenabling the user to use the computer system more quickly andefficiently.

In some embodiments, if the process for creating the user interface forthe respective computer system (e.g., 600B) using the first userinterface template is continued without installing the first applicationon the respective computer system, the first user interface, once usedon the respective computer system (e.g., as a watch face userinterface), does not include the first user interface element (e.g.,where the user interface elements can include one or more of 636A, 638A,640A, 642A, 644A, 646A, 648A, 650A; 636B, 638B, 640B, 642B, 644B, 646B,648B, and/or 650B) corresponding to the first application. In someembodiments, if the process for creating the user interface for therespective computer system using the first user interface template iscontinued without installing the first application on the respectivecomputer system but with installing a second application on therespective computer system, where the second application corresponds toa second user interface element (e.g., where the user interface elementscan include one or more of 636A, 638A, 640A, 642A, 644A, 646A, 648A,650A; 636B, 638B, 640B, 642B, 644B, 646B, 648B, and/or 650B) of thefirst user interface template, then the first user interface, once usedon the respective computer system (e.g., as a watch face userinterface), does not include the first user interface elementcorresponding to the first application but includes the second userinterface element corresponding to the second application. Not includingthe first user interface element if the process for creating the userinterface for the respective computer system using the first userinterface template is continued without installing the first applicationon the respective computer system prevents the user interface from beingcreated with a feature that may not properly function (e.g., because thecorresponding first application is not installed), thereby enhancing theoperability of the computer system and making the user-system interfacemore efficient.

In some embodiments, in accordance with the determination that the firstapplication is not available on (e.g., not downloaded on; not installedon; not accessible on) the respective computer system (e.g., 600B)(e.g., as shown in FIG. 6N), the computer system (e.g., 600A; 600B)continues the process for (e.g., as shown in FIGS. 6F-6G, 6I-6J, and/or6L-6R) creating the user interface for the respective computer systemusing the first user interface template, where continuing the processincludes installing (e.g., by downloading and/or purchasing therespective application (e.g., from an app store)) the first applicationon the respective computer system (e.g., as shown in FIGS. 6N-6P). Insome embodiments, the first user interface template maintains the firstuser interface element corresponding to the first application.

In some embodiments, in response to completing the process (e.g., asshown in FIGS. 6F-6G, 6I-6J, and/or 6L-6R) for creating the userinterface for the respective computer system (e.g., 600B) using thefirst user interface template, the computer system (e.g., 600A; 600B)adds (e.g., initiating a process for adding) the user interface createdusing the first user interface template to a user interface library(e.g., a watch face library; a library of available watch faces that canbe set as the current watch face for the respective computer system) forthe respective computer system (e.g., a smartwatch). In someembodiments, in response to completing the process for creating the userinterface and/or upon determining that the process for creating the userinterface has been completed, the respective computer systemautomatically sets the user interface created using the first userinterface template as a currently selected user interface (e.g., asshown by 656B in FIG. 6G, 6114B in FIG. 6K, and 699B in FIG. 6S) fromthe user interface library for the respective computer system (e.g., asthe current watch face of the computer system). In some embodiments, inresponse to completing the process for creating the user interface forthe respective computer system using the first user interface template,the computer system also displays (or causes display of), via thedisplay generation component, an option to install one or moreapplications on the respective computer system corresponding toapplications that were not available on the respective computer systemand were, during the process for creating the user interface for therespective computer system using the first user interface template, notselected to be made available on the respective computer system.Providing the option to install one or more applications on therespective computer system corresponding to applications that are stillnot available on the respective computer system in response tocompleting the process for creating the user interface enables a user toquickly and easily download the unavailable applications even after theprocess has been completed. Providing improved control options enhancesthe operability of the computer system and makes the user-systeminterface more efficient

In some embodiments, the representation (e.g., 600A; 600B) of the userinterface specifies elements (e.g., 636A; 636B; 644A; 644B) for thefirst application that is not available on (e.g., not installed on; notdownloaded onto; not locally accessible on) the respective computersystem (e.g., 600B). In some embodiments, the process for creating theuser interface for the respective computer system includes, inaccordance with a determination that the first application is to be madeavailable (e.g., installed) on (e.g., to be downloaded and installed on)the respective computer system (e.g., based on receiving a userindication or detecting one or more user inputs to install the firstapplication on the respective computer system), the computer systeminitiating a process for making the first application available (e.g.,installing) on the respective computer system, where, after completingthe process for creating the user interface for the respective computersystem using the first user interface template, the user interfacecreated using the first user interface template is displayed on therespective computer system with the first user interface element (e.g.,the first watch complication) corresponding to the first application;and in accordance with a determination that the first application is notto be made available on (e.g., not to be downloaded and/or installed on)the respective computer system (e.g., based on receiving a userindication or detecting one or more user inputs to not install the firstapplication on the respective computer system), the computer systemforgoing initiating the process for making the first applicationavailable (e.g., installing) on the respective computer system, where,after completing the process for creating the user interface for therespective computer system using the first user interface template, theuser interface created using the first user interface template isdisplayed on the respective computer system without the first userinterface element.

In some embodiments, the computer system (e.g., 600A; 600B) displays (orcauses display of) the representation (e.g., 634A; 634B) of the firstuser interface template during the process for creating the userinterface for the respective computer system using the first userinterface template. In some embodiments, the first user interfacetemplate includes the first user interface element (e.g., the firstwatch complication) corresponding to the first application at a firstlocation within the first user interface template. In some embodiments,the first user interface template includes one or more additional userinterface elements (e.g., corresponding to different watch complicationpreviews). In some embodiments, the one or more additional userinterface elements are displayed at particular defined locations withinthe first user interface template.

In some embodiments, after creating the user interface using the firstuser interface template, the respective computer system (e.g., 600B)displays the user interface (e.g., 697; 679; as a watch face) createdusing the first user interface template, where the user interfaceincludes the first user interface element (e.g., the first watchcomplication) corresponding to the first application at the firstlocation (e.g., at the same location within the user interface that thefirst user interface element was displayed within the first userinterface template). In some embodiments, other user interface elementsare also displayed at corresponding locations within the user interfacedisplayed on the respective computer system.

In some embodiments, if the first application was not available on therespective computer system (e.g., 600B) and the first application wasnot subsequently installed on the respective computer system, therespective computer system displays the user interface (e.g., 697; 679;as a watch face) created using the first user interface template, wherethe user interface does not include the first user interface element(e.g., the first watch complication) corresponding to the first userinterface element and the first application at the first location (e.g.,the same location within the user interface that the first userinterface element was located in the first user interface template). Insome embodiments, the other user interface elements (e.g., if theircorresponding applications had been or were made available on therespective computer system) are still displayed at their correspondinglocations within the user interface displayed on the respective computersystem.

In some embodiments, after completing the process for (e.g., as shown inFIGS. 6F-6G, 6I-6J, and/or 6L-6R) creating the user interface for therespective computer system (e.g., 600B) using the first user interfacetemplate (e.g., and thus the user interface created using the first userinterface template is ready to be displayed or used as a watch face),the computer system (e.g., 600A; 600B) causes display of (e.g., on therespective computer system; if the computer system is the same system asthe respective computer system, on the computer system) the userinterface created using the first user interface template (e.g., asshown by 656A and 656B in FIG. 6G, 6106A and 6114B in FIG. 6K, and 699Aand 699B in FIG. 6S), where the first user interface element displayedin the user interface includes information (e.g., location information;date/time information; weather information; calendar information)obtained from the first application (e.g., related to a feature of thefirst application). In some embodiments, prior to causing display of theuser interface created using the first user interface template, thecomputer system (e.g., 600) completes the process for creating the userinterface for the respective computer system using the first userinterface template. Displaying information obtained from the firstapplication in the first user interface element displayed in the userinterface provides a user with quick and easy access to the informationwithout requiring an input to launch the application to obtain theinformation. Reducing the number of inputs needed to perform anoperation enhances the operability of the computer system and makes theuser-system interface more efficient (e.g., by helping the user toprovide proper inputs and reducing user mistakes whenoperating/interacting with the computer system) which, additionally,reduces power usage and improves battery life of the computer system byenabling the user to use the computer system more quickly andefficiently.

In some embodiments, the information (e.g., location information;time/date information) included in the first user interface elementdisplayed in the user interface (e.g., 697; 679) corresponds to locationinformation (e.g., and the first application corresponds to a mapapplication or a GPS-based application), and the information isdetermined (e.g., selected) based on a location setting (e.g., a pre-setlocation configuration or setting) from the first user interfacetemplate, where the location setting is configured to be a currentlocation of the respective computer system (e.g., 600B). Configuring(e.g., automatically) the location setting to be a current location ofthe respective computer system enables a user to not have to provideadditional inputs to manually set the location setting to the currentlocation. Reducing the number of inputs needed to perform an operationenhances the operability of the computer system and makes theuser-system interface more efficient (e.g., by helping the user toprovide proper inputs and reducing user mistakes whenoperating/interacting with the computer system) which, additionally,reduces power usage and improves battery life of the computer system byenabling the user to use the computer system more quickly andefficiently.

In some embodiments, the first user interface template, when received,was configured/setup for location information to be based on a currentlocation of its source computer system or source device; in someembodiments in which this is the case, in the user interface createdusing the first user interface template, the information isautomatically set to include location information that is based on thecurrent location of the respective computer system (e.g., 600B).

In some embodiments, the information (e.g., location information;time/date information) included in the first user interface elementdisplayed in the user interface (e.g., 697; 679) corresponds to locationinformation (e.g., and the first application corresponds to a mapapplication or a GPS-based application), and the information isdetermined (e.g., selected) based on a location setting (e.g., a pre-setlocation configuration or setting) from the first user interfacetemplate, where the location setting is configured to be a designatedlocation different from a current location of the respective computersystem (e.g., 600B). In some embodiments, the first user interfacetemplate, when received, was configured/setup for location informationto be based on a location different from the current location of itssource computer system or source device; in some embodiments in whichthis is the case, in the user interface created using the first userinterface template, the information is automatically set to includelocation information that corresponds to that same different locationfrom the source computer system or source device. Automatically (e.g.,without user input) setting the information to include locationinformation that corresponds to that same different location from thesource computer system or source device results in the user interfacemaintaining a setting from the first user interface template, as mayhave been the user's preference, thereby enhancing the operability ofthe computer system and making the user-system interface more efficient.

In some embodiments, the information included in the first userinterface element displayed in the user interface (e.g., 697; 679)corresponds to calendar information (e.g., schedule information; meetinginformation), and the information is determined based on applicationinformation from the first application accessed via the respectivecomputer system (e.g., 600B), where the first application corresponds toa calendar application. In some embodiments, in the user interfacecreated using the first user interface template, the information isautomatically set to include schedule information that is based on acalendar application that is accessible on or by the respective computersystem. Automatically setting the information to include scheduleinformation that is based on the calendar application that is accessibleon or by the respective computer system enables a user to not have toprovide additional inputs to manually set the calendar settings for theuser interface. Reducing the number of inputs needed to perform anoperation enhances the operability of the computer system and makes theuser-system interface more efficient (e.g., by helping the user toprovide proper inputs and reducing user mistakes whenoperating/interacting with the computer system) which, additionally,reduces power usage and improves battery life of the computer system byenabling the user to use the computer system more quickly andefficiently.

In some embodiments, the first user interface template, when received,is configured to (e.g., set to) include (e.g., automatically include) avisual characteristic (e.g., a color, such as a background color and/orcolor scheme) that is selected based on context information accessibleby (e.g., determinable by; detectable by) the respective computer system(e.g., 600B). In some embodiments, the visual characteristic includes abackground color or background color scheme for the user interface, andthe context information includes a color or color scheme of a housing ofthe computer system (e.g., an electronic device) or of a deviceaccessory (e.g., case; cover) detected by (e.g., using one or more imagesensors) the respective computer system.

In some embodiments, the respective computer system (e.g., 600B; arespective device) is a particular type or model within a device typecategory (e.g., a particular type or model of smartwatch). In someembodiments, in accordance with the determination that the firstapplication is not available on the respective computer system, thecomputer system (e.g., 600A; 600B) detects (e.g., via one or more inputdevices that are in communication with the computer system) a request(e.g., user selection of the alert or an affordance in the alertindicating that the first application needs to be installed on therespective computer system in order for the first user interfacetemplate to be used to create a user interface for the respectivecomputer system that includes the first user interface element from thefirst user interface template) to install (e.g., download and install)the first application on the respective computer system. In someembodiments, in response to detecting the request to install the firstapplication on the respective computer system, in accordance with adetermination that the first application cannot be installed on therespective computer system (e.g., because the first application cannotbe downloaded on the respective computer system; because the firstapplication is not compatible with the respective computer system), thecomputer system displays, via the display generation component, anindication (e.g., 635C; 635D; 635E; a notification; an error message)that the first application cannot be installed on the respectivecomputer system. Displaying the indication that the first applicationcannot be installed on the respective computer system enables a user toquickly and easily recognize that the operation cannot be performed onthe computer system. Providing improved visual feedback enhances theoperability of the computer system and makes the user-system interfacemore efficient (e.g., by helping the user to provide proper inputs andreducing user mistakes when operating/interacting with the computersystem) which, additionally, reduces power usage and improves batterylife of the computer system by enabling the user to use the computersystem more quickly and efficiently. In some embodiments, in accordancewith a determination that the first application can be installed on therespective computer system (e.g., 600B), the computer system (e.g.,600A; 600B) (if the computer system is the respective computer system)automatically downloads and installs the first application or causes (ifthe computer system is different from the respective computer system)the respective computer system to download and install the firstapplication.

The foregoing description, for purpose of explanation, has beendescribed with reference to specific embodiments. However, theillustrative discussions above are not intended to be exhaustive or tolimit the invention to the precise forms disclosed. Many modificationsand variations are possible in view of the above teachings. Theembodiments were chosen and described in order to best explain theprinciples of the techniques and their practical applications. Othersskilled in the art are thereby enabled to best utilize the techniquesand various embodiments with various modifications as are suited to theparticular use contemplated.

Although the disclosure and examples have been fully described withreference to the accompanying drawings, it is to be noted that variouschanges and modifications will become apparent to those skilled in theart. Such changes and modifications are to be understood as beingincluded within the scope of the disclosure and examples as defined bythe claims.

What is claimed is:
 1. A computer system, comprising: a displaygeneration component; one or more processors; and memory storing one ormore programs configured to be executed by the one or more processors,the one or more programs including instructions for: receiving arepresentation of a first user interface template that specifies anarrangement of user interface elements including a first user interfaceelement corresponding to a first application and one or more other userinterface elements corresponding to software that is different from thefirst application; subsequent to receiving the representation of thefirst user interface template, receiving a request to use the first userinterface template for a respective computer system that includes aplurality of installed applications; and in response to receiving therequest to use the first user interface template for the respectivecomputer system, initiating a process for creating a user interface forthe respective computer system using the first user interface template,wherein the process for creating the user interface for the respectivecomputer system using the first user interface template includes: inaccordance with a determination that the first application is notavailable on the respective computer system, concurrently displaying,via the display generation component, a representation of the first userinterface template and an alert indicating that the first applicationneeds to be installed on the respective computer system in order for thefirst user interface template to be used to create a user interface forthe respective computer system that includes the first user interfaceelement from the first user interface template; and in accordance with adetermination that the first application is available on the respectivecomputer system, forgoing displaying, via the display generationcomponent, the alert indicating that the first application needs to beinstalled on the respective computer system in order for the first userinterface template to be used to create a user interface for therespective computer system that includes the first user interfaceelement from the first user interface template.
 2. The computer systemof claim 1, wherein the process for creating the user interface for therespective computer system using the first user interface templateincludes: in accordance with the determination that the firstapplication is not available on the respective computer system,displaying, via the display generation component, an affordance that,when activated, initiates a process for installing the first applicationon the respective computer system.
 3. The computer system of claim 2,wherein the process for creating the user interface for the respectivecomputer system using the first user interface template includes: inaccordance with a determination that the affordance was not activated,continuing the process for creating the user interface for therespective computer system using the first user interface templatewithout installing the first application on the respective computersystem, wherein the first user interface template is configured to notinclude the first user interface element corresponding to the firstapplication.
 4. The computer system of claim 2, further comprisingduring the process for creating the user interface for the respectivecomputer system using the first user interface template includes: whiledisplaying the affordance: detecting an activation of the affordance;and in response to detecting the activation of the affordance,initiating the process for installing the first application on therespective computer system.
 5. The computer system of claim 1, whereinthe one or more other user interface elements include a second userinterface element corresponding to a second application different fromthe first application, and wherein the process for creating the userinterface for the respective computer system using the first userinterface template includes: in accordance with a determination that thesecond application is not available on the respective computer system,displaying, via the display generation component, a second alertindicating that the second application needs to be installed on therespective computer system in order for the first user interfacetemplate to be used to create a user interface for the respectivecomputer system that includes the second user interface element from thefirst user interface template; and in accordance with a determinationthat the second application is available on the respective computersystem, forgoing displaying, via the display generation component, thesecond alert indicating that the second application needs to beinstalled on the respective computer system in order for the first userinterface template to be used to create a user interface for therespective computer system that includes the second user interfaceelement from the first user interface template.
 6. The computer systemof claim 1, wherein the one or more other user interface elementsinclude a second user interface element corresponding to a secondapplication different from the first application and a third userinterface element corresponding to a third application different fromthe first application and the second application, and wherein theprocess for creating the user interface for the respective computersystem using the first user interface template includes: subsequent todisplaying the alert: in accordance with a determination that the secondapplication is not available on the respective computer system,displaying, via the display generation component, a second alertindicating that the second application needs to be installed on therespective computer system in order for the first user interfacetemplate to be used to create a user interface for the respectivecomputer system that includes the second user interface element from thefirst user interface template; and subsequent to displaying the secondalert: in accordance with a determination that the third application isnot available on the respective computer system, displaying, via thedisplay generation component, a third alert indicating that the thirdapplication needs to be installed on the respective computer system inorder for the first user interface template to be used to create a userinterface for the respective computer system that includes the thirduser interface element from the first user interface template.
 7. Thecomputer system of claim 1, wherein the representation of the userinterface specifies elements for the first application that is notavailable on the respective computer system and a second applicationthat is not available on the respective computer system and the processfor creating the user interface for the respective computer system usingthe first user interface template includes: displaying, via the displaygeneration component, a user interface for the first user interfaceelement that includes a representation of the first user interfacetemplate and one or more selectable user interface objects associatedwith the first user interface element, wherein the representation of thefirst user interface template includes the first user interface elementcorresponding to the first application; and while displaying therepresentation of the first user interface template, and after receivingone or more inputs corresponding to a decision as to whether to make thefirst application available, receiving an input corresponding to arequest to display a user interface for a second user interface elementthat includes a representation of the first user interface template andone or more selectable user interface objects associated with the seconduser interface element; and in response to receiving the request todisplay a user interface for the second user interface element: inaccordance with a determination that the first application was selectedfor installation on the respective computer system, displaying the userinterface for the second user interface element includes displaying arepresentation of the first user interface element; and in accordancewith a determination that the first application was not selected forinstallation on the respective computer system, displaying the userinterface for the second user interface element includes displaying therepresentation of the first user interface template without displayingthe first user interface element.
 8. The computer system of claim 7,wherein the representation of the user interface specifies elements fora third application that is not available on the respective computersystem and the process for creating the user interface for therespective computer system using the first user interface templateincludes: while displaying the representation of the first userinterface template, and after receiving one or more inputs correspondingto a decision as to whether to make the second application available,receiving an input corresponding to a request to display a userinterface for a third user interface element that includes arepresentation of the first user interface template and one or moreselectable user interface objects associated with the third userinterface element; and in response to receiving the request to display auser interface for the third user interface element: in accordance witha determination that the second application was selected forinstallation on the respective computer system, displaying the userinterface for the third user interface element includes displaying arepresentation of the second user interface element; and in accordancewith a determination that the second application was not selected forinstallation on the respective computer system, displaying the userinterface for the third user interface element includes displaying therepresentation of the first user interface template without displayingthe second user interface element.
 9. The computer system of claim 1,wherein the process for creating the user interface for the respectivecomputer system using the first user interface template includes:displaying, via the display generation component, the representation ofthe first user interface template; and while displaying therepresentation of the first user interface template: in accordance withthe determination that the first application is not available on therespective computer system, displaying, in the representation of thefirst user interface template, the first user interface element with afirst visual characteristic; and in accordance with the determinationthat the first application is available on the respective computersystem, displaying, in the representation of the first user interfacetemplate, the first user interface element with a second visualcharacteristic different from the first visual characteristic.
 10. Thecomputer system of claim 1, wherein receiving the representation of thefirst user interface template comprises receiving the representation ofthe first user interface template via a messaging application.
 11. Thecomputer system of claim 1, wherein receiving the representation of thefirst user interface template includes: displaying, via the displaygeneration component, a messaging user interface of a messagingapplication; and displaying, in the messaging user interface, a firstmessage corresponding to the representation of the first user interfacetemplate, wherein the first message includes an image showing therepresentation of the first user interface template.
 12. The computersystem of claim 1, wherein the process for creating the user interfacefor the respective computer system using the first user interfacetemplate includes: in accordance with the determination that the firstapplication is not available on the respective computer system:initiating a communication to a second computer system that is coupledto the computer system, wherein the communication includes instructionsto continue the process for creating the user interface for therespective computer system using the first user interface template onthe second computer system.
 13. The computer system of claim 1, whereinthe process for creating the user interface for the respective computersystem using the first user interface template includes: in accordancewith the determination that the first application is not available onthe respective computer system: continuing the process for creating theuser interface for the respective computer system using the first userinterface template without installing the first application on therespective computer system, wherein the first user interface template nolonger includes the first user interface element corresponding to thefirst application.
 14. The computer system of claim 1, the one or moreprograms further including instructions for: adding the user interfacecreated using the first user interface template to a user interfacelibrary for the respective computer system.
 15. The computer system ofclaim 1, wherein the representation of the user interface specifieselements for the first application that is not available on therespective computer system, the process for creating the user interfacefor the respective computer system includes: in accordance with adetermination that the first application is to be made available on therespective computer system: initiating a process for making the firstapplication available on the respective computer system, wherein, aftercompleting the process for creating the user interface for therespective computer system using the first user interface template, theuser interface created using the first user interface template isdisplayed on the respective computer system with the first userinterface element corresponding to the first application; and inaccordance with a determination that the first application is not to bemade available on the respective computer system: forgoing initiatingthe process for making the first application available on the respectivecomputer system, wherein, after completing the process for creating theuser interface for the respective computer system using the first userinterface template, the user interface created using the first userinterface template is displayed on the respective computer systemwithout the first user interface element.
 16. The computer system ofclaim 1, the one or more programs further including instructions for:causing display of the user interface created using the first userinterface template, wherein the first user interface element displayedin the user interface includes information obtained from the firstapplication.
 17. The computer system of claim 16, wherein: theinformation included in the first user interface element displayed inthe user interface corresponds to location information, and theinformation is determined based on a location setting from the firstuser interface template, wherein the location setting is configured tobe a current location of the respective computer system.
 18. Thecomputer system of claim 16, wherein: the information included in thefirst user interface element displayed in the user interface correspondsto location information, and the information is determined based on alocation setting from the first user interface template, wherein thelocation setting is configured to be a designated location differentfrom a current location of the respective computer system.
 19. Thecomputer system of claim 16, wherein: the information included in thefirst user interface element displayed in the user interface correspondsto calendar information, and the information is determined based onapplication information from the first application accessed via therespective computer system, wherein the first application corresponds toa calendar application.
 20. The computer system of claim 16, wherein thefirst user interface template, when received, is configured to include avisual characteristic that is selected based on context informationaccessible by the respective computer system.
 21. The computer system ofclaim 1, the one or more programs further including instructions for: inaccordance with the determination that the first application is notavailable on the respective computer system: detecting a request toinstall the first application on the respective computer system; and inresponse to detecting the request to install the first application onthe respective computer system: in accordance with a determination thatthe first application cannot be installed on the respective computersystem, displaying, via the display generation component, an indicationthat the first application cannot be installed on the respectivecomputer system.
 22. A non-transitory computer-readable storage mediumstoring one or more programs configured to be executed by one or moreprocessors of computer system that is in communication with a displaygeneration component, the one or more programs including instructionsfor: receiving a representation of a first user interface template thatspecifies an arrangement of user interface elements including a firstuser interface element corresponding to a first application and one ormore other user interface elements corresponding to software that isdifferent from the first application; subsequent to receiving therepresentation of the first user interface template, receiving a requestto use the first user interface template for a respective computersystem that includes a plurality of installed applications; and inresponse to receiving the request to use the first user interfacetemplate for the respective computer system, initiating a process forcreating a user interface for the respective computer system using thefirst user interface template, wherein the process for creating the userinterface for the respective computer system using the first userinterface template includes: in accordance with a determination that thefirst application is not available on the respective computer system,concurrently displaying, via the display generation component, arepresentation of the first user interface template and an alertindicating that the first application needs to be installed on therespective computer system in order for the first user interfacetemplate to be used to create a user interface for the respectivecomputer system that includes the first user interface element from thefirst user interface template; and in accordance with a determinationthat the first application is available on the respective computersystem, forgoing displaying, via the display generation component, thealert indicating that the first application needs to be installed on therespective computer system in order for the first user interfacetemplate to be used to create a user interface for the respectivecomputer system that includes the first user interface element from thefirst user interface template.
 23. A method, comprising: at a computersystem that is in communication with a display generation component:receiving a representation of a first user interface template thatspecifies an arrangement of user interface elements including a firstuser interface element corresponding to a first application and one ormore other user interface elements corresponding to software that isdifferent from the first application; subsequent to receiving therepresentation of the first user interface template, receiving a requestto use the first user interface template for a respective computersystem that includes a plurality of installed applications; and inresponse to receiving the request to use the first user interfacetemplate for the respective computer system, initiating a process forcreating a user interface for the respective computer system using thefirst user interface template, wherein the process for creating the userinterface for the respective computer system using the first userinterface template includes: in accordance with a determination that thefirst application is not available on the respective computer system,concurrently displaying, via the display generation component, arepresentation of the first user interface template and an alertindicating that the first application needs to be installed on therespective computer system in order for the first user interfacetemplate to be used to create a user interface for the respectivecomputer system that includes the first user interface element from thefirst user interface template; and in accordance with a determinationthat the first application is available on the respective computersystem, forgoing displaying, via the display generation component, thealert indicating that the first application needs to be installed on therespective computer system in order for the first user interfacetemplate to be used to create a user interface for the respectivecomputer system that includes the first user interface element from thefirst user interface template.